[BUG?] gpgme 0.9.0 & passphrase oddity

[Albrecht Dreß]

Gpgme 0.9.0 seems to behave differently if the passphrase is entered  
directly or through gpg-agent/pinentry.

If I do not have an egent running, the passphrase callback is called, and  
if I cancel there, gpgme_op_sign() correctly returns with an error.

With the agent running, it pops up pinentry. When I select cancel there,  
gpgme_op_sign() returns with no error, and all subsequent operations on  
the signature of course will fail.

Is this the intended behaviour? IMHO, it would be nicer if gpgme_op_sign  
(and friends) would return ERR_CANCEL in *both* cases.

I use gpg-agent (GnuPG) 1.9.8, gpg 1.2.4, and pinentry 0.7.0.

TIA, 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: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : /pipermail/attachments/20040708/deb89309/signature.bin