Import Key failed (web)
I just reinstalled GPGTools under OSX Lion (10.7.2). When I tried to import my private key from disk, the import failed. I was able to import my public key from the key server successfully.
I looked to see if I could open my private key file as text and then copy/paste it into GPG Keychain Access, but I couldn't see a way to do that.
What's my next step?
Doug Nix
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Alex on 24 Dec, 2011 06:39 AM
Hi Doug,
could you give us the console output when trying to import the key?
See http://support.gpgtools.org/kb/faq/how-can-i-generate-debugging-inf...
You have three ways to import the key:
Best regards, Alex
2 Posted by Doug Nix on 25 Dec, 2011 02:37 AM
Alex,
Thanks for getting back to me on Christmas Eve!
Here's the Console Log Data:
I ran the GPGTools diagnostics commands in Terminal, but both lines cam back with "Command Not Found".
Momentum:~ dougnix$ $ curl -OL http://github.com/GPGTools/GPGTools_Core/raw/master/scripts/debugGPGTools.sh
-bash: $: command not found
Momentum:~ dougnix$ $ LANG=C sh debugGPGTools.sh
-bash: $: command not found
There were no Mail errors in the logs.
Here's the installer log:
I get an error code "0" when I try to import the key, no matter what way I try to do it. Here are the error dialogs:
Thanks for any help you can provide!
Doug Nix
Support Staff 3 Posted by Luke Le on 25 Dec, 2011 04:02 AM
Hi Doug,
from your attachments we're able to tell that the
extension of your key file is .txt and not only .pgp
Please try to remove the .txt part and retry to import the key.
The wrong extension might throw off GPG Keychain Access.
Sometimes OS X fails to change extensions, if so, please post the path
where your file is located and we'll send you a Terminal command you can use to change it.
Support Staff 4 Posted by Luke Le on 25 Dec, 2011 04:05 AM
.txt would work if you exported the key as ASCII text, yours was exported as binary.
5 Posted by Alex on 08 Jan, 2012 11:52 AM
Hi Doug, do you still have the same issue with the latest version of GPG Keychain Access? Best regards, Alex
6 Posted by Doug Nix on 09 Jan, 2012 04:59 PM
Alex,
I've had zero success in dealing with this problem. I still get the same error messages.
The file was generated as an .asc, not a binary. I was not able to get the command lines you provided to run in terminal, so I guess I'm stuck.
Any other thoughts you have are welcomed. I really don't know what to do next.
Regards,
Doug Nix
H: (519) 650-5979
M: (519) 729-5704
F: (519) 653-1318
email: [email blocked]
Request a meeting: http://tungle.me/dougnix
Find me LinkedIn at http://www.linkedin.com/in/dougnix
Support Staff 7 Posted by Luke Le on 09 Jan, 2012 05:04 PM
Hi Doug,
the simplest thing would be to have a screen sharing session so we can debug the problem on your computer.
Since that's a very sensitive operation we completely understand if that's no option for you.
8 Posted by Doug Nix on 09 Jan, 2012 05:10 PM
Luke,
I'm a Mac user, so we'd need to do that via Skype. are you OK with that?
Doug Nix
[email blocked]
Murphy's Law has now been officially re-named The Certainty Principle
Support Staff 9 Posted by Luke Le on 09 Jan, 2012 05:12 PM
I've been having problems with Skype and screen sharing, but TeamViewer is a great solution which works on the mac.
http://www.teamviewer.com/download/version_6x/TeamViewerQS.dmg
Would you be ok with that?
Also could you send an email to my address [email blocked] with your skype account, so we can chat?
10 Posted by Doug Nix on 12 Jan, 2012 06:15 PM
Luke,
I'm online if you want to screen share with me to work on the private key issue I'm having.
Doug Nix
[email blocked]
"Live as if you were to die tomorrow. Learn as if you were to live forever." Mahatma Gandhi
Support Staff 11 Posted by Luke Le on 12 Jan, 2012 06:59 PM
Closing this now, and if you run into problems again, simply open a new discussion :)
Luke Le closed this discussion on 12 Jan, 2012 06:59 PM.