
Verifying: signed and encrypted gpg files should get verified
Reported by Alex (via GPGTools) | April 18th, 2011 @ 08:27 PM | in 1.6
Comments and changes to this ticket
-
ronin-140089 (at lighthouseapp) April 18th, 2011 @ 10:10 PM
Huh? They get. Not with the file verification UI, but with a simple dialog. I'm not sure how much work it would be to refactor the code to work with general data instead of files.
Encrypt+Signed files get first signed and then encrypted. You can't verify a encrypted file without prior decrypting it.
-
Alex (via GPGTools) April 18th, 2011 @ 10:31 PM
I see. Then it's a special case of #55. Currently when I validate a signed+encrypted file I see a window "Verification Results" with an empty table.
-
Alex (via GPGTools) April 23rd, 2011 @ 12:38 AM
- State changed from open to resolved
(from [1032797ecf6b7af7fb1185bd5c0de1fa93b8b916]) Improved verification [#58 state:resolved] [#55 state:resolved] https://github.com/GPGTools/GPGServices/commit/1032797ecf6b7af7fb11...
-
steve June 18th, 2015 @ 04:22 PM
- State changed from resolved to released
- Importance cleared.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
People watching this ticket
Referenced by
-
58 Verifying: signed and encrypted gpg files should get verified (from [1032797ecf6b7af7fb1185bd5c0de1fa93b8b916]) Improve...
-
55 Verifying: 'no verifiable data found' (from [1032797ecf6b7af7fb1185bd5c0de1fa93b8b916]) Improve...