Damien, I've filed the same bug with Enigmail and received an answer saying basically: “It's not bug, it's a feature!” More specifically:
"""
The "problem" is that GPG_AGENT_INFO is set by your distribution, i.e.
your distribution starts an instance of gpg-agent during the login
process.If the environment variable is set, then Enigmail will always
usegpg-agent - that's how I intend Enigmail to work. In other words,
gpg-agent is only not used, if no GPG_AGENT_INFO variable is set and
ifyou use gpg 1.x.
The option is only there to force the use of gpg-agent for gpg 1.4.x
installations.
"""
(I do use 1.4.x version of GnuPG, btw, but GnuPG 2.x is available on the
system and apparently that's enough.)
The fix is simple, find components/enigmail.js under the Enigmail
extension directory and change line:
useAgent = (this.gpgAgentInfo.envStr.length>0 ||
this.prefBranch.getBoolPref("useGpgAgent"));
to:
useAgent = (this.gpgAgentInfo.envStr.length>0 &&
this.prefBranch.getBoolPref("useGpgAgent"));
and unchecking the appropriate option in Enigmail preferences will work
as sane user would expect.
Cheers,
Marcel
signature.asc
Description: OpenPGP digital signature
