Store keychain .gnupg in an encrypted place
Which of our tools is giving you problems? (possible options: GPGMail, GPGServices, GPG Keychain Access, …)
GPG Keychain Access
What’s the version of that tool? (read the following knowledge base article to learn how to find a tool's version: http://support.gpgtools.org/kb/faq/where-can-i-find-the-version-inf...)
Version 1.1.3 (601)
downloaded the new Version that was released for OS X Maverick
What version of OS X are you using? (e.g.: 10.8.4, 10.7.5)
Please describe your problem. Add as much detail as possible.
Some of our whistleblowing clients would like to keep their GPG keychain .gnupg folder in a safer place like an encrypted container since their collection of keys might already be compromising. In 10.8 it was easy: the .gnupg folder was moved to such a container and at its original place the user simply had to create an alias that pointed to the new location of .gnupg.
In Maverick this doesn't seem to work: "Someone tampered with your installation of pin entry-mac" (see attached screeshot)
Any idea how this could be solved?
Please describe what you did expect instead
I think being able to choose the location of your keychain is a requirement that many users should need. Our solution in 10.8 was a workaround and we might have to find a new workaround solution soon. But on the long run, this should become a feature of GPG Preferences and the Suite.
If you remember, please describe the steps leading up to the problem
[Steps go here]
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 Luke Le on 24 Oct, 2013 03:42 PM
the place of the .gnupg folder can be wherever you want, as long as it is found by gnupg.
The pinentry error is unrelated to this.
Could you please try to remove the entire /usr/local/MacGPG2 folder and install the suite again? That should make the problem go away.
2 Posted by jmarks on 24 Oct, 2013 04:00 PM
Yes - this solved my problem. The alias works .
Maybe you can include "Choose location of your key chain:" as a new feature in one of your next releases?
Support Staff 3 Posted by Luke Le on 31 Oct, 2013 03:52 PM
we're indeed already planning such an option, but still have to find a way, how to best implement this.
You can track progress here:
Luke Le closed this discussion on 31 Oct, 2013 03:56 PM.
Steve re-opened this discussion on 29 Jul, 2014 05:46 PM
Steve closed this discussion on 29 Jul, 2014 05:47 PM.