Disable "Save in Keychain" in Pinentry Mac
Which of our tools is giving you problems? Pinentry Mac
Attach a screenshot of the version info for all installed components (how to: https://gpgtools.tenderapp.com/kb/faq/where-can-i-find-version-info...):
Describe your problem. Add as much detail as possible. Looking through the implementation of pinentry-mac at https://github.com/GPGTools/pinentry-mac, it seems that it might be possible to disable the "Store in Keychain" functionality all together. If the "cache-id" variable is set somewhere to some value, it won't prompt or save it in the macos keychain.
I know it's possible to uncheck the checkmark using the If the GPG Suite System preferences, but I like to get rid of the option completely as I really don't want to (accidentally) store my gpg password in the macos keychain.
Could you let me know if this is possible?
My research so far:
"cache-id" configuration variable (?) being read: https://github.com/GPGTools/pinentry-mac/blob/8d811e25d58e88d804f61...
Here is the conditional using cacheId actually going to save it into macos keychain:
What did you expect instead Not have the "Save in Keychain" checkbox in the Pinentry Mac pop-up.
Describe steps leading to the problem. Whenever he Pinentry Mac pop-up opens.
Are you using any other Mail.app plugins? No
- GNU_Tools_versions.jpg 208 KB
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 13 Dec, 2019 11:44 AM
welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.
Please excuse the late reply. We were currently seeing a large influx of support request which we are working through as fast as we can.
If you want to disable the "store in keychain" option, this KB-article explains how to do that:
Please let us know if that worked as expected.
All the best,
Support Staff 2 Posted by Steve on 13 Dec, 2019 11:45 AM
Edit: Here is the correct KB link:
Steve closed this discussion on 04 Mar, 2020 02:29 PM.