gpgme bug: verify + failed auto key retreival?

[Albrecht Dreß]

Am 27.01.04 20:45 schrieb(en) Marcus Brinkmann:
> The only "solution" without using a different gpg is to remove some  
> error
> checks from GPGME entirely, which will trigger new bugs (like gpgme
> reporting success when validating certain invalid messages or
> signatures).
> Frankly, I am at a loss what the best solution is here.

Maybe this is a too simplistic view, but looking at the log I see a  
sequence of

[GNUPG:] NODATA 1
[GNUPG:] IMPORT_RES 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[GNUPG:] ERRSIG D43F8AD8A1EE605F 17 2 00 1074795554 9
[GNUPG:] NO_PUBKEY D43F8AD8A1EE605F

replies coming from gpg. If (and only if!) this is a safe indication for a  
missing public key (#3 + 4) which could not be retreived from the key  
server (#1 + 2), you could catch it (might make some "look ahead" code  
necessary, though), skip messages #1 and #2 and continue processing the  
signature as if no auto-retreive had been initiated/failed. In all other  
cases, the return value would be "no data". This would resolve this very  
specific but important case for real-life apps.

Just my € 0.01...
Cheers, Albrecht.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Albrecht Dreß  -  Johanna-Kirchner-Straße 13  -  D-53123 Bonn (Germany)
       Phone (+49) 228 6199571  -  mailto:albrecht.dress at arcor.de
_________________________________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : /pipermail/attachments/20040128/71e011da/attachment.bin