I receive the following error message after upgrading to Enigmail 0.95.0 from 0.94.0: enigmail> /usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2 -d --use-a gent gpg: problem with the agent - disabling agent use gpg: can't query passphrase in batch mode gpg: Invalid passphrase; please try again ... gpg: can't query passphrase in batch mode gpg: Invalid passphrase; please try again ... gpg: can't query passphrase in batch mode gpg: encrypted with 4096-bit ELG-E key, ID XXXXXXXXX, created XXXXXXXXXXXX XXXXXXXXXX@XXXXXXXXXXX gpg: encrypted with 2048-bit ELG-E key, ID XXXXXXXXX, created XXXXXXXXXXXX XXXXXXXXXX@XXXXXXXXXXX gpg: public key decryption failed: bad passphrase gpg: decryption failed: secret key not available enigmail.js: Enigmail.decryptMessageEnd: Error in command execution
I should also add that: - I do not and never did use the gpg-agent - the "Use agent" flag is disabled in config (checked both on the raw config and on the interface)
Additional infos I found: if $GPG_AGENT_INFO is set to any value, enigmail will "presume" that you want to use it... in fact if I manually unset it everything works as expected. So ... why and where is this variable set ? :D
No idea, tried with a clean profile?
Do you mean a clean thunderbird profile (then it doesn't matter: the variable is set system-wide), or a clean system user profile ? If the latter... I have a distinct feeling that the culprit is keychain. I changed its invocation from: .bash_profile:keychain ~/.ssh/id_rsa .bash_profile:[ -f $HOME/.keychain/$HOSTNAME-sh ] && \ .bash_profile: . $HOME/.keychain/$HOSTNAME-sh .bash_profile:[ -f $HOME/.keychain/$HOSTNAME-sh-gpg ] && \ .bash_profile: . $HOME/.keychain/$HOSTNAME-sh-gpg to .bash_profile:keychain --agents ssh ~/.ssh/id_rsa .bash_profile:[ -f $HOME/.keychain/$HOSTNAME-sh ] && \ .bash_profile: . $HOME/.keychain/$HOSTNAME-sh .bash_profile:[ -f $HOME/.keychain/$HOSTNAME-sh-gpg ] && \ .bash_profile: . $HOME/.keychain/$HOSTNAME-sh-gpg to no avail...
correction: commenting also the two .bash_profile:[ -f $HOME/.keychain/$HOSTNAME-sh-gpg ] && \ .bash_profile: . $HOME/.keychain/$HOSTNAME-sh-gpg lines, that environment variable disappears. It's a bit awkward, but I figure this solves the problem ...
Is this still an issue?
With that "fix", no, it's not. Maybe some more definitive solution can be found ? :)
(In reply to comment #1) > - the "Use agent" flag is disabled in config IMHO, *this* is the core of the problem! I have a related problem here: TB crashes each time I save the message in the "compose" window. When I looked into the list of running processed, I noticed that TB now tries to start gpg-agent each time a message is saved - no matter whether the message needs uses signatures/encryption or not! And in my case this will crash TB, because gpg-agent tries to access its keyring which is located on an encrypted partition which I only mount on a as-needed basis. As I see it, there are actually two bugs: * The "use gpg-agent" Setting in the Enigmail Plugin preferences is completely ignored * gpg-agent is started for each composed message, and not only when using encryption or digital signatures with this message. I have to add, this was not a problem with previous versions of TB/Enigmail - it's a new bug.
Cough, can we just forget about this and close it... ? :)
(In reply to comment #9) > Cough, can we just forget about this and close it... ? :) Well, as upstream clearly has no intention of fixing this, I'd suggest we close it with resolution WONTFIX. It's sort of annoying that gpg-agent is started unconditionally, but it seems we'll have to live with it.
Following reporter advice, I close it to WONTFIX. If you got this bug and have something to add, do not hesitate to reopen it.
