
Sign and encrypt should not create a separate file
Reported by Alex (via GPGTools) | March 28th, 2011 @ 11:08 AM | in Q1 2011
See http://www.gnupg.org/documentation/manuals/gnupg/gpg_002dzip.html how GnuPG implements it.
Comments and changes to this ticket
-
ronin-140089 (at lighthouseapp) March 28th, 2011 @ 02:31 PM
- State changed from open to hold
- Assigned user changed from ronin-140089 (at lighthouseapp) to Alex (via GPGTools)
Shouldn't be a problem, although I think it's important to be able to generate detached signatures too. How should we implement that?
-
-
ronin-140089 (at lighthouseapp) March 28th, 2011 @ 04:04 PM
- State changed from hold to open
- Assigned user changed from Alex (via GPGTools) to ronin-140089 (at lighthouseapp)
Sounds good; it would be pretty useless to make Sign create a non-detached signature on arbitrary (e.g binary files).
-
-
Alex (via GPGTools) March 30th, 2011 @ 05:44 PM
- State changed from open to resolved
(from [fb408b006441e7fe70b1e7c00cdc5c5271903957]) Inline-signing when encrypting a file [#35 state:resolved] https://github.com/GPGTools/GPGServices/commit/fb408b006441e7fe70b1...
-
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
Attachments
Referenced by
-
35 Sign and encrypt should not create a separate file (from [fb408b006441e7fe70b1e7c00cdc5c5271903957]) Inline-...