PEP-8-ify a bit Not done yet, but this is much better already. Should be no functional changes
Fix sigcheck pgp/mime processing with gnupg 2 gnupg 2.1 in stretch doesn't like MD5.
gpg2 output differs from gpg1 - fix GPGSearch
More lax with mime
ud-echelon fixes
try to properly handle some more mime stuff. - use email module instead of deprecated mimetools and multifile modules - changes: sigcheck ud-echelon ud-mailgate userdir_gpg.py - move ud-echelon and sigcheck to GPGCheckSig2 interface.
Dead import
Get rid of tabs
ud-mailgate: fix gpg result usage We use the result of the pgp check for quite a long time in the main program. Give it its own variable instead of using Res which was overwritten a bit later. Also make a new gpgcheck2 class that allows us to access the values of the gpg signature check in a saner way.
userdir_gpg.py: add a ClearKeyrings()
Print gpg's exit status when it fails
Aha. Error is not some magic variable or exception, it's a normal string that needs defining when we use it.
Check if a key has encryption capabilities and fail saying so when trying to encrypt stuff (like passwords) to users. All this does is give nicer error messages, it previously failed with just "gpg failed".
Check that the primary key is not expired, even if we get a GOODSIG status from gnupg. Based on patch by Jeremy T. Bouse
ud-info: fix changing of DD status/DD status comment - we were missing prompt information so we got a backtrace. ud-info: Warn when we don't have a prompt string for attributes on startup.
* Remove use of deprecated functions from the string module
RT #70: Fix SUBKEY signatures; update some error cases to more recent gpgv docs
Removed reference to FCNTL since it is not required anymore and the LOCK_EX is now in fcntl (and working similar).
Create ~/.gnupg if it does not exist since gpg will fail fatally otherwise
Patch by Andreas Barth: added --secret-keyring /dev/null This is required for ud-mailgate to work with sarge as well. The semantics of the option --no-default-keyring of GnuPG has been changed between woody and sarge: --no-default-keyring Do not add the default keyrings to the list of keyrings. Note that GnuPG will not operate without any keyrings, so if you use this option and do not provide alternate keyrings via --keyring or --secret-keyring, then GnuPG will still use the default public or secret keyrings. (and won't work if they don't exist)