Description of problem: When I receive gpg encrypted email that is not directed to my main key gnome-keyring asks for the passphrase and decrypts the message. Enigmail then has this security info: Enigmail Security Info Decrypted message Error - no matching private/secret key found to decrypt message gpg: Note: signatures using the MD5 algorithm are rejected gpg: Oops: keyid_from_fingerprint: no pubkey gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system! (etc) With gnome-keyring disabled enigmail is unable to decrypt the message. It then cannot find the key pair corresponding to the message despite these being present in my keyring. Version-Release number of selected component (if applicable): thunderbird-enigmail-1.8.1-1.fc20.x86_64 How reproducible: receive gpg encrypted email Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Where is the info on how to properly set up a system with enigmail so it can decrypt all messages that it currently cannot without gnome-keyring?
When a message encrypted to my main key is received (the one I use most), gnome keyring asks for the passphrase for that key and the message is decrypted. Enigmail still complains: Decrypted message Error - no matching private/secret key found to decrypt message gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system! (etc) It mentions the subkey ID but not the main key. Details -> View key properties works OK though. Obviously I want enigmail to correctly locate the keys that are present and decrypt all stuff without complaining.
When I kill the gnome keyring daemon before starting thunderbird stuff (to avoid hijaacking) doesn't work. Log says stuff like: [GNUPG:] NEED_PASSPHRASE [bleep] gpg: can't connect to the agent - trying fall back gpg: problem with the agent: No pinentry [GNUPG:] ERROR get_passphrase 85 [GNUPG:] MISSING_PASSPHRASE pinentry is installed and available.
Without gnome keyring daemon the pinentry issue persists even after trying the pinentry-curses tip from https://chaosfreakblog.wordpress.com/2013/06/21/gpg-problem-with-the-agent-no-pinentry-solved/. Thus enigmail cannot decrypt mail without gnome keyring.
Finally found this page: https://www.enigmail.net/support/gnupg2_issues.php I installed pinentry-qt and removed /etc/gnupg/*. Then stuff started to work again. Maybe make the pinentry issue more promomently known to the user?
*** Bug 1215316 has been marked as a duplicate of this bug. ***
Please which version of gpg is used ? (/usr/bin/gpg2 or /usr/bin/gpg) displayed in enigmail preferences menu
(In reply to Remi Collet from comment #6) > Please which version of gpg is used ? > (/usr/bin/gpg2 or /usr/bin/gpg) displayed in enigmail preferences menu gpg2 is mentioned # which gpg2 /bin/gpg2 # rpm -qf /bin/gpg2 gnupg2-2.0.27-1.fc20.x86_64
> Then stuff started to work again. So closing this one.