GpgME BUG: list expired secret keys?

Albrecht Dreß albrecht.dress at arcor.de
Sat Apr 21 16:22:09 CEST 2007


Am 13.04.07 00:58 schrieb(en) Marcus Brinkmann:
> If you run with GPGME_DEBUG=3 or just run gpg --status-fd 2 manually, you will probably find that this is because gpg does return incomplete data.  As far as I understand, gnupg's key listing output of secret keys is currently not fully complete in the manner you noticed before. Can you confirm that this is the problem in your case?

I tried again with my test application, and the GPGME debug output is attached.  I tested with a dummy key, so no confidential data has been removed from the logs.  Please note that I meanwhile upgraded to gpg 1.4.7 and gpgme 1.1.4:

---snip-----------------------------
[albrecht at antares ~]$ GPGME_DEBUG=3:expire-sec.log ./gpgme-key-expire test.key at some.org 1
now is 1177164586
key: can_sign=1 can_encrypt=0 expired=0
  subkey id=5AF280F9940BBECD can_sign=1 can_encrypt=0 expired=0 expires=1177073638 [1]
  subkey id=4450EFC17F688538 can_sign=0 can_encrypt=1 expired=0 expires=1177073658 [1]
[albrecht at antares ~]$ GPGME_DEBUG=3:expire-pub.log ./gpgme-key-expire test.key at some.org 0
now is 1177164730
key: can_sign=1 can_encrypt=0 expired=1
  subkey id=5AF280F9940BBECD can_sign=1 can_encrypt=0 expired=1 expires=1177073638 [1]
  subkey id=4450EFC17F688538 can_sign=0 can_encrypt=1 expired=1 expires=1177073658 [1]
---snip-----------------------------

GnuPG spits out several "expired" messages in both cases, as you can see in the logs.

For the time being, I will supply a patch for Balsa checking if the secret key has expired or not, but IMO gpgme *must* return a correct value here!

Cheers, Albrecht.


--
 Albrecht Dreß  -  Johanna-Kirchner-Straße 13  -  D-53123 Bonn (Germany)
       Phone (+49) 228 6199571  -  mailto:albrecht.dress at arcor.de
  GnuPG public key:  http://www.mynetcologne.de/~nc-dreszal/pubkey.asc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: expire-pub.log
Type: text/x-log
Size: 3406 bytes
Desc: not available
Url : /pipermail/attachments/20070421/26ff4474/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: expire-sec.log
Type: text/x-log
Size: 4413 bytes
Desc: not available
Url : /pipermail/attachments/20070421/26ff4474/attachment-0001.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : /pipermail/attachments/20070421/26ff4474/attachment.pgp 


More information about the Gnupg-devel mailing list