"Send Keys Failed! Code=0"
I've tried uploading my public key to a/the key server, but I keep getting the same error message. I checked a few of the posts, and went back to GPG Keychain Access' Preferences to select a key server. However, there are no key servers listed in the drop-down menu. None. Keychain Access is v.1.0b7, and its update check says that's the latest version. (I've already installed the latest GPGMail-latest, timestamped 5:01 p.m. 25 September 2012.)
Any ideas on how to get my key-server list to populate?
-Jess
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
Support Staff 1 Posted by Luke Le on 26 Sep, 2012 09:57 AM
Hi Jess,
please also install the nightly of GPG Keychain Access from https://nightly.gpgtools.org
We'll have official releases soon, but the nightlies are the most stable ones at the moment!
2 Posted by Jess W. Driskel... on 26 Sep, 2012 03:58 PM
Luke:
Thanks for the link to the nightlies. I downloaded all the latest elements (Keychain Access, Preferences, and Services) and installed them.
GPG Keychain Access (KA) v.1.0b8 returns the following failures for two different key servers....
gpg: sending key nnnnnnnn to hkp server pool.sks-keyservers.net
gpg: keyserver timed out
gpg: keyserver send failed: Keyserver error
gpg: sending key nnnnnnnn to hkp server pgp.mit.edu
gppg: keyserver timed out
gpg: keyserver send failed: Keyserver error
Oh well, at least 1.0b8 correctly populates the key server list.
Any further ideas?
-Jess
Support Staff 3 Posted by Luke Le on 26 Sep, 2012 04:00 PM
Hmm... are you behind a proxy or a pretty strict firewall?
That's sometimes a problem.
4 Posted by Jess W. Driskel... on 26 Sep, 2012 04:18 PM
Luke:
I have the OS firewall turned on with stealth mode activated. I also have the SPI firewall turned on in the router/gateway (as well as the usual NAT firewall). Other than that--as in a firewall with exceptionally restrictive policies--I don't think my firewall is that strict. Is there perhaps some non-standard port I should turn on?
-Jess
Support Staff 5 Posted by Luke Le on 26 Sep, 2012 06:42 PM
Keyservers usually listen to port 11371. So if you have block outgoing ports, you'll have to open them.
Other than that, you could try the following keyserver (works over HTTP):
http://pgp.mit.edu/
Simply enter it in GPG Keychain Access under preferences.
(the http:// prefix is important, otherwise hkp is used again)
6 Posted by Jess W. Driskel... on 26 Sep, 2012 06:54 PM
Luke:
I finally succeeded in getting KA to upload the key to pool.sks-keyservers.net. But KA didn't do it without some guidance....
Because of your comment,
> (the http:// prefix is important, otherwise hkp is used again)
I checked KA's preferences. None of the key servers is listed with a protocol. So I went back to pool.sks-keyservers.net and added the "hkp://" protocol specification. The key was uploaded with no problem.
So, the problem with KA lies in the way the key servers are listed in the app and in GPGPreferences: you need to add the protocol to each listing.
-Jess
Support Staff 7 Posted by Luke Le on 26 Sep, 2012 07:01 PM
Hi Jess,
unfortunately GPG Keychain Access has a known bug where sometimes
the communication with keyservers fails.
While it would be a nice explanation, unfortunately I don't think that's the problem.
As you see in the error you posted before, the protocol is correctly detected even without the prefix.
So I wonder if this was coincidence.
We'll have to test this thoroughly. Thanks for the hint!
8 Posted by Jess W. Driskel... on 28 Sep, 2012 05:12 AM
Luke:
You were right about the protocol spec. Adding the protocol for the sks-keyserver got it to upload, but another attempt without the addition of the protocol immediately after worked also.
I just tried adding the http protocol to the head of the MIT URL, but I got an immediate send error, so I tried removing the protocol. Oddly enough, it worked. Go figure....
In any case, the problem seems to be resolved for me.
Thanks for all your help. You guys are so far ahead of any other developers in the encryption market that they should all hang their heads in shame.
-Jess
Support Staff 9 Posted by Luke Le on 28 Sep, 2012 03:32 PM
Yeah, this might be the old bug. We hope to get this fixed soon, so it finally works reliably and always.
In addition keyservers themselves are not always reliable.
Thanks for the very kind words! It's great to hear when our users are satisfied :)
Support Staff 10 Posted by Luke Le on 28 Sep, 2012 03:32 PM
Closing this discussion. Feel free to open a new one anytime!
Luke Le closed this discussion on 28 Sep, 2012 03:32 PM.