pyme for debugging gpgme applications, new verifydetails.py

[Bernhard Reiter]

I have attached a new verifydetails.py to
https://sourceforge.net/tracker/index.php?func=detail&aid=2013640&group_id=104883&atid=639601

It helps to debug how applications deal with gpgme result values
E.g. here is an example output

python examples/verifydetails.py ~/tmp/y.sig ~/tmp/dbgmd-00001.verify
gpgme version: 1.1.6
engines:
/usr/bin/gpg2 2.0.9
/usr/bin/gpgsm 2.0.9
OpenPGP True
CMS True

trying to verify signature /home/bernhard/tmp/y.sig for 
file /home/bernhard/tmp/dbgmd-00001.verify
signature 1 :
  summary:     0x800
  status:      0x7000001
  timestamp:   1215123456
  fingerprint: XXXXXXXXXXXXX
  uid:         XXXXXXXXXXXXXXXXXXXXX

You can use "gpg-error" to decipher the "status" value:

$ LANG=C gpg-error 0x7000001
117440513 = (7, 1) = (GPG_ERR_SOURCE_GPGME, GPG_ERR_GENERAL) = (GPGME, General 
error)

To me this has been helpful in analysing if gpgme or Kontact/KMail or both 
contribute to a problematic behaviour that can be observed.
It overcomes the obstacle that "gpg2" or "gpgsm" on the command line 
might behave a bit differently as compared when being called via gpgme,
e.g. here are much more return values to consider.

Best,
Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1603 bytes
Desc: not available
URL: </pipermail/attachments/20080708/c8e562df/attachment.bin>