I also see this bug since a few weeks both with GPG Suite and with MacPorts GnuPG, and it is quite Heisenberg'sch. The passphrase is correctly stored in the Mac Keychain, and it gets correctly retrieved when the gpg-agent/pinentry-mac is started from gpg in the terminal. It instead if stopped working when the call to gpg (same binary, same gpghome) comes from inside an application (here: Enigmail).
Deleting the entries from the keychain(!) and re-storing the passphrase "fixes" the problem, with only one apparent difference to the entry in the keychain: the name of the entry now sports the fingerprint in the parens, while previously all entries ended with "()".
The presence of the old entry with just "()" seems to make the difference.
By the way, hitting "cancel" on the pinentry-mac now deletes valid entries from the keychain, which is clearly a bug too.
Comments are currently closed for this discussion. You can start a new one.
|?||Show this help|
|ESC||Blurs the current field|
|r||Focus the comment reply box|
|^ + ↩||Submit the comment|
You can use
Command ⌘ instead of
Control ^ on Mac
Support Staff 1 Posted by Steve on 01 Sep, 2019 12:30 PM
welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.
Do you have MacGPG and MacPorts installed now? If so, could you temporarily remove any custom gpg and see if that solves the problems.
We tried but couldn't reproduce the problem you mention about pinentry mac usage resulting in deleted entries from macOS keychain. Are you able to reliably reproduce the problem? if so, could you please send exact reporduce steps.
Just updated Thunderbird to v68 with Enigmail 2.1.2. Was able to send and receive encrypted and signed emails fine with 2019.1 installed. What versions are you using?
All the best,
Support Staff 2 Posted by Steve on 01 Sep, 2019 12:30 PM
P.S.: We would kindly ask you to create a new discussion, whenever you need assistance with GPG Suite, even if your problem looks similar to the one you are replying to. While the symptoms are often very much alike, the root cause often differs. Having separate discussions allows to focus better on your particular issue.
To proceed we have split your comment into a separate discussion.
Support Staff 3 Posted by Steve on 01 Sep, 2019 03:19 PM
quick update about this problem.
the solution to this problem is to lock and unlock your login keychain, easiest to do via logout or restart.
The issue you are seeing is a bug in macOS Mojave which we have filed with Apple back in Mai 2019. They have fixed the problem in macOS 10.15 Catalina. Our question if they are planning to backport the fix to macOS 10.14 remains unanswered as of now.
We have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll stay in the loop and get notified as soon as we have news. Feel free to open a new discussions should you run into further problems or need assistance.
All the best,
Steve closed this discussion on 18 Sep, 2019 02:33 PM.