[BUG/Gpgme] checking message with a revoked key

Marcus Brinkmann marcus.brinkmann at ruhr-uni-bochum.de
Fri May 21 18:44:41 CEST 2004

At Fri, 21 May 2004 14:00:07 +0200,
Albrecht Dreß wrote:
> Wow - great patch!! Now op_verify correctly returns with no error, writes  
> back the "decrypted" contents, and the signature status says "certificate  
> revoked". Good work!!

Ok, as Werner said CERT_REVOKED is ok, I added the patch to CVS.
> > BTW, the CERT_REVOKED error code in the patch is probably bogus.  From
> > a quick glance, I agree with you that a KEY_REVOKED error code is
> > needed in gpg-error.
> Now I'm looking eagerly forward to a new gpgme/gpg-error tarball 2B  
> released soon, so I can feed the fix and the new key status/error upstream  
> into balsa... ;-))

There is more that needs to be fixed and prepared, but a new release
won't take too long, stay tuned ;)

You can already add the code to handle it to balsa, as we use the
existing GPG_ERR_CERT_REVOKED error code.


More information about the Gnupg-devel mailing list