Am 08.03.07 17:04 schrieb(en) Adam Schreiber:
> AFAIK, the incompatibilities only show up where users
have installed
> gpg2 and not the other. As for elaboration, because I
haven't
> experienced the bugs myself, I can point you at a bug
report in GNOME
> Bugzilla [1].
I can confirm that gpgme 1.1.3 and gnupg 2.0.2 do not
interact properly
when using it in the MUA balsa.
As an example, try to sign a message, i.e. create a context,
select the
signer's key, create the input and output data objects, and
then call
gpgme_op_sign(). Gpg-agent kicks in and calls pinentry to
read the
passphrase of the secret key. Now click cancel in pinentry
- and
gpgme_op_sign() will return with exit code 0! The gpgme
debug log
(balsa-gpgme.log) of this operation is attached.
Replacing gpg2 by gpg 1.4.5, everything works flawlessly
(see attached log
balsa-gpgme-1.4.log). Please note that at the end of this
log, apparently
more information about the failed operation is available (fd
33:
"MISSING_PASSPHRASE",
"BAD_PASSPHRASE").
This problem might be related to a different one [1] I
reported a few
weeks ago, unfortunately without any feedback yet.
I'm using a PowerMac running Yellowdog Linux (kernel
2.6.19.1) with glibc
2.3.4 and gcc 3.4.4, if this is important.
Cheers, Albrecht.
[1] http://lists.gnupg.org/pipermail/gnupg-dev
el/2007-February/023676.html
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~
Albrecht Dreß - Johanna-Kirchner-Straße 13 - D-53123
Bonn (Germany)
Phone (+49) 228 6199571 -
mailto:albrecht.dress arcor.de
GnuPG public key: htt
p://www.mynetcologne.de/~nc-dreszal/pubkey.asc
____________________________________________________________
_____________
_______________________________________________
Gnupg-devel mailing list
Gnupg-devel gnupg.org
h
ttp://lists.gnupg.org/mailman/listinfo/gnupg-devel
|