Page MenuHome GnuPG
Create Task
Maniphest T1030

GPGME reporting End of file (7,16383) for missing CRL for users own key
Closed, ResolvedPublic
Actions

Description

Architecture: powerpc
Source: gnupg2 Version: 2.0.11-1kk1
Source: gpgme1.0 Version: 1.1.8-0kk1
Source: kdepim Version: 4:4.1.1.enterprise4.0.20090306.935937-kk1
Package: dirmngr Version: 1.0.1-3

There is a report for kontact:
https://www.intevation.de/roundup/kolab/kolab/issue3583 (offline s/mime
signing without CRL for secret key gives unkown system error)

The CRL for one of my signing keys expired (I was offline so I could not get a
new one) and it seems that gpgme does not communicate this condition properly.




still lists three secret keys



[the status of the certificate is unknown]
[validation model used: shell]
[certificate is bad: No CRL known]



with Debian Lenny's python-pyme and testCMSgetkey.py v20080813:



python testCMSgetkey.py



9C:F8:E2:A0:0B:1E:E4:BF:02:66:2A:69:3B:85:F7:4F:46:C6:5E:78

pyme.errors.GPGMEError: GPGME: End of file (7,16383)



Werner, maybe this is better in the current development version of gpgsm?
Details
Version 
1.1.8 
Event Timeline
bernhard added projects: S/MIME, kks, Bug Report, gpgme.Apr 24 2009, 11:14 AM
bernhard set Version to 1.1.8.
bernhard added subscribers: • werner, bernhard.
• werner assigned this task to marcus.Apr 27 2009, 10:06 AM
• werner added a subscriber: marcus.
• werner added a comment.May 26 2009, 2:00 PM
Marcus, can you please have a look at this?
marcus added a comment.Aug 11 2009, 2:27 PM
Sorry for the delay.  I can not access the kolab tracker (404), has the link

changed?  Errors for individual keys in a keylisting are not available in

detail, but only the invalid flag is set.  When using an invalid key, a more

detailed reason may be available.  There is currently no way to get more

detailed reasons about why a key in a key listing is invalid.



You may want to try with more recent version of packages, in particular dirmngr

seems rather old.



I don't know where pyme gets its EOF error value from, maybe you can translate

this to gpgme operations or provide a GPGME debug log?
bernhard added a comment.Aug 11 2009, 4:36 PM
Sorry, typo in the URL, (there was one "kolab/" too much, but you could have 

gotten to it via the main page. :) )

https://www.intevation.de/roundup/kolab/issue3583 (offline s/mime signing 

without CRL for secret key gives unkown system error)



You could try it yourself with pyme, but if you are saying that there were

enought changes to warrant a retest, I will retest with a new version.
marcus added a comment.Jan 8 2010, 3:23 PM
Hi Bernhard,



Did you try with a new version?  Did it work better?  Thanks!
bernhard added a comment.Jan 11 2010, 2:53 PM
Marcus, not yet so far. I would appreciate a test on your end, as I might not 

get to the issue for a while. There should be enough information to reproduce 

the issue.
• werner closed this task as Resolved.May 22 2013, 2:53 PM
• werner added a project: Too Old.
Too much changed in the last 3 years, it does not make sense to follow up on

this bug.  Feel free to re-open if you can replicate it with current releases.