OK, so pinentry-gtk or similar works fine. So gnupg2 and pinentry-\
I do not have a gpg-agent.conf file
That's OK, typically, you don't need one.
I got the error message "ERR 280 not implemented"
So gnome-keyring-gpg is still active (and superseeded gnupg-agent).
Have you DISABLED gnome-keyring-gpg as suggested in the FAQ in step 4?
Here's how I did it: First, check whether you have /etc/xdg/autostart/gnome-keyring-gpg.desktop: ls /etc/xdg/autostart/gnome-keyring-gpg.desktop
If so, either edit it and set X-GNOME-AutoRestart to false or simple move it using mv /etc/xdg/autostart/gnome-keyring-gpg.desktop /etc/xdg/autostart/gnome-keyring-gpg.desktop.disabled
I added "use-agent" to gpg.conf, rebooted and now...
On Ubuntu, upstart is used. There, the existence of "use-agent" is checked in /usr/share/upstart/sessions/gpg-agent.conf (line 10). On debian, the same is done in /etc/X11/Xsession.d/90gpg-agent (line 6). So, by entering "use-agent" in gpg.conf, gpg-agent is started on next login, but unfortunately gnome-keyring-gpg is NOT disabled by those scripts (which I consider a bug since their co-existence always causes headaches).
I am not asked for a passphrage, and Messages are neither decryted nor encrypted.
Well, neither of them works properly now. Disable gnome-keyring-gpg, log out and log in and you should be fine.
Can you help me activate gpg-agent and direct Enigmail to it
You already did that.
GPG4Win (v2.3) and Enigmail (1.9.1) I have in the WinPC are not giving me any troubles, but I already disabled automatic update because I am afraid of the consequences.
GPG4Win works fine since Microsoft does not try to be smart by integrating a non-fully functional key manager in windows. There is no need to block GPG4win or Enigmail updates. It's just necessary to work around some cliffs in Gnome.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In every case you should ensure that the files to be moved already exist. If not, or you're feeling unsafe, please ask for advice on Debian support channels. You could also ask on our mailing list (enigmail-users@enigmail.net), as the Debian mainainer for Enigmail and GnuPG is an active member there.
It's no wonder, why gpg-agent works out of the box on Windows and Mac OS X: There is simply no other software which could interfere like Gnome Keyring or KDE-Wallet on linux systems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried to follow the suggestions in this thread, but my experience with Linux is still very limited and I was always afraid of making things worse. None of those solutions I tried worked, but I found in another blog an advice that resolved the problem.
/ I removed the current version of Enigmail.
/ Installed the old version 1.8.2 (last of the 1.8.x)
/ Disabled auto update.
One problem remains:-
I only have to enter the passphrase once, when I start thunderbird, and after that decryption is always automatic. This is not very secure, but there is no way in the Debian "Keys" to set an expiry time for remembering the passphrase.
I don't think this is a very elegant solution, but we will have to wait for the Enigma and Debian developers to work together for a better way of doing this otherwise we can never update to newer versions of Enigmail. I suspect the Key management in the Debian package needs further work.
I thank all participants in this thread for their advice.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, so pinentry-gtk or similar works fine. So gnupg2 and pinentry-\
That's OK, typically, you don't need one.
So gnome-keyring-gpg is still active (and superseeded gnupg-agent).
Have you DISABLED gnome-keyring-gpg as suggested in the FAQ in step 4?
Here's how I did it: First, check whether you have /etc/xdg/autostart/gnome-keyring-gpg.desktop:
ls /etc/xdg/autostart/gnome-keyring-gpg.desktopIf so, either edit it and set X-GNOME-AutoRestart to false or simple move it using
mv /etc/xdg/autostart/gnome-keyring-gpg.desktop /etc/xdg/autostart/gnome-keyring-gpg.desktop.disabledOn Ubuntu, upstart is used. There, the existence of "use-agent" is checked in /usr/share/upstart/sessions/gpg-agent.conf (line 10). On debian, the same is done in /etc/X11/Xsession.d/90gpg-agent (line 6). So, by entering "use-agent" in gpg.conf, gpg-agent is started on next login, but unfortunately gnome-keyring-gpg is NOT disabled by those scripts (which I consider a bug since their co-existence always causes headaches).
Well, neither of them works properly now. Disable gnome-keyring-gpg, log out and log in and you should be fine.
You already did that.
GPG4Win works fine since Microsoft does not try to be smart by integrating a non-fully functional key manager in windows. There is no need to block GPG4win or Enigmail updates. It's just necessary to work around some cliffs in Gnome.
Hi, I can only say how to disable gnome keyring on Ubuntu-based systems. Type these two commands in a Terminal window:
Afterwards log out and log in again.
In every case you should ensure that the files to be moved already exist. If not, or you're feeling unsafe, please ask for advice on Debian support channels. You could also ask on our mailing list (enigmail-users@enigmail.net), as the Debian mainainer for Enigmail and GnuPG is an active member there.
It's no wonder, why gpg-agent works out of the box on Windows and Mac OS X: There is simply no other software which could interfere like Gnome Keyring or KDE-Wallet on linux systems.
I tried to follow the suggestions in this thread, but my experience with Linux is still very limited and I was always afraid of making things worse. None of those solutions I tried worked, but I found in another blog an advice that resolved the problem.
/ I removed the current version of Enigmail.
/ Installed the old version 1.8.2 (last of the 1.8.x)
/ Disabled auto update.
One problem remains:-
I only have to enter the passphrase once, when I start thunderbird, and after that decryption is always automatic. This is not very secure, but there is no way in the Debian "Keys" to set an expiry time for remembering the passphrase.
I don't think this is a very elegant solution, but we will have to wait for the Enigma and Debian developers to work together for a better way of doing this otherwise we can never update to newer versions of Enigmail. I suspect the Key management in the Debian package needs further work.
I thank all participants in this thread for their advice.