python-gnupg/gnupg
Isis Lovecruft 16107bc8a8
Workaround possible upstream GnuPG bug sign fail when passphrase=''.
If passed `--passphrase-fd 0` and piped the passphrase `''` (an empty
string), GnuPG will truncate the message being signed. The truncation
appears to only affect messages which contain newlines; for those
messages, the first line (up unto and including the newline character)
will be truncated and thus missing from the output signed message or
signature, causing verification for signatures on the original
non-truncated message to fail.

 * FIXES #82: https://github.com/isislovecruft/python-gnupg/issues/82
2015-03-18 19:33:09 +00:00
..
test Add two more signature passphrase tests with bytes literals for #82. 2015-03-18 19:31:33 +00:00
__init__.py fix sphinx errors&warnings; some pep8 2013-10-14 01:24:17 -03:00
_ansistrm.py Change LICENSE to GPLv3+, after discussion with intrigeri. 2013-07-27 19:27:53 +00:00
_logger.py more py2.6 fixes 2014-04-23 14:49:24 +02:00
_meta.py Workaround possible upstream GnuPG bug sign fail when passphrase=''. 2015-03-18 19:33:09 +00:00
_parsers.py Handle [GOOD|BAD|MISSING]_PASSPHRASE statuses in _parsers.ListPackets. 2015-03-11 03:25:55 +00:00
_trust.py properly pass argument during trustdb repair 2014-10-02 04:56:56 -05:00
_util.py Workaround possible upstream GnuPG bug sign fail when passphrase=''. 2015-03-18 19:33:09 +00:00
_version.py Change versioneer parameters in gnupg/_version.py to match setup.py. 2014-11-19 21:44:53 +00:00
copyleft.py Change LICENSE to GPLv3+, after discussion with intrigeri. 2013-07-27 19:27:53 +00:00
gnupg.py Fix UnicodeDecodeError in gen_key() when run with PyPy. 2015-03-18 05:00:00 +00:00