[Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card

[Patrick Brunschwig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> Patrick Brunschwig schrieb:
>>> Patrick Brunschwig schrieb:
>>>> Stefan Xenon wrote:
>>>>> Hi!
>>>>> I use GnuPG2 and tried to generate a key on the OpenPGP Card.
>>>>> Unfortunately it failed with the error message "unbekannter Fehler bei
>>>>> Schlüsselgenerierung" (unknown error). The Enigmail console tells me the
>>>>> following command is executed:
>>>>> C:\Program Files\GNU\GnuPG2\gpg2.exe --charset utf8 --no-tty --status-
>>>>> fd 1 --logger-fd 1 --command-fd 0 --with-colons --card-edit
>>>>> It works on the same system when configuring Enigmail to use GnuPG v1.
>>>>> So maybe an compatibility issue with GnuPG v2?
>>>> Yes, an incompatibility with GnuPG v2. I have fixed this a few days ago.
>>>>
>>>> In order to use gpg2, you will need a trunk version of Enigmail. Please
>>>> also note that generating keys and administration of GnuPG cards is
>>>> broken in Enigmail v0.96.0; it will be fixed in the next version of
>>>> Enigmail.
>>>>
>>> Also I experience that the Enigmail option, how long to store the
>>> passphrase, does not work with GnuPG. Is it possible to fix it for the
>>> next version please?
>>> Also I would be interested to know when you schedule to release the next
>>> version (roughly)?
>> (Please place replies below the rest of the conversations.)
>>
>> With GnuPG 2, gpg-agent must be used (no way to avoid it). Therefore it
>> is not possible to control the duration of how long the passphrase is
>> remembered, since passphrase-remembering is handled by gpg-agent -- it
>> cannot be fixed in Enigmail by any means.
>>
>> If you want to change the passhprase timeout settings, you'll need to
>> create a gpg-agent.conf file in the same directory as your gpg.conf file.
>>
>> The next release will be ready when it's ready. Sorry, I can't be more
>> precise than this.
>>
Stefan Xenon wrote:
> If Enigmail can not handle the duration of pass phrase caching along
> with GnuPG2 , I would propose to detect whether GnuPG v2 is used and to
> disable such option appropriately (and also displaying the reason in the
> configuration dialog).
>
> This would reduce user's confusion. Also note that GnuPG v2 is supposed
> to replace v1 in the future so that this will become a more relevant
topic.


done in v0.96.0

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBSm6rz3cOpHodsOiwAQiTPwf7BQyN2v+yuTIz/V3PHj0Z2f0qRKUAI/jx
mHuCF7z8Wua2OHPLJa+OOYivFM5tt35uPA0Z2J5DgLpEm6wY83TKw9mjOUtYr6PW
yzzs7g+jxxAldEqGeb9kAty0hLNSkmuS/j9IJI3/lYh2h0b7QR1jgYEl+L/0Vaw0
/yb4x2ltuwGXiFUvn6SHXPhIA/ht0nEa2BtZyUwU4hU8+m+M3Rucoit9+9VkENeZ
RHdR7E0yoFLjK9HWMn+R9hsO0l5hv6xGU3PYsRdPmGMdIvi/ZBh4Bd0KgB1JmT6w
M2mU5ITuCJx3UForq3Xdqyg9UMu8nc9LhmtbX0EMcprVtixH43ophg==
=7w0W
-----END PGP SIGNATURE-----