tag:gpgtools.tenderapp.com,2011-11-04:/discussions/problems/2051-send-keys-failed-code0GPGTools: Discussion 2012-10-09T22:18:27Ztag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-26T09:57:58Z2012-09-26T09:57:58Z"Send Keys Failed! Code=0"<div><p>Hi Jess,</p>
<p>please also install the nightly of GPG Keychain Access from
<a href=
"https://nightly.gpgtools.org">https://nightly.gpgtools.org</a><br>
We'll have official releases soon, but the nightlies are the most
stable ones at the moment!</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-26T15:58:40Z2012-09-26T15:58:40Z"Send Keys Failed! Code=0"<div><p>Luke:</p>
<p>Thanks for the link to the nightlies. I downloaded all the
latest elements (Keychain Access, Preferences, and Services) and
installed them.</p>
<p>GPG Keychain Access (KA) v.1.0b8 returns the following failures
for two different key servers....</p>
<p>gpg: sending key nnnnnnnn to hkp server pool.sks-keyservers.net
gpg: keyserver timed out gpg: keyserver send failed: Keyserver
error</p>
<p>gpg: sending key nnnnnnnn to hkp server pgp.mit.edu gppg:
keyserver timed out gpg: keyserver send failed: Keyserver error</p>
<p>Oh well, at least 1.0b8 correctly populates the key server
list.</p>
<p>Any further ideas?</p>
<p>-Jess</p></div>Jess W. Driskelltag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-26T16:00:29Z2012-09-26T16:00:29Z"Send Keys Failed! Code=0"<div><p>Hmm... are you behind a proxy or a pretty strict firewall?<br>
That's sometimes a problem.</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-26T16:18:06Z2012-09-26T16:18:06Z"Send Keys Failed! Code=0"<div><p>Luke:</p>
<p>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?</p>
<p>-Jess</p></div>Jess W. Driskelltag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-26T18:42:03Z2012-09-26T18:42:03Z"Send Keys Failed! Code=0"<div><p>Keyservers usually listen to port 11371. So if you have block
outgoing ports, you'll have to open them.</p>
<p>Other than that, you could try the following keyserver (works
over HTTP):<br>
<a href="http://pgp.mit.edu/">http://pgp.mit.edu/</a><br>
Simply enter it in GPG Keychain Access under preferences.<br>
(the http:// prefix is important, otherwise hkp is used again)</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-26T18:54:58Z2012-09-26T18:54:58Z"Send Keys Failed! Code=0"<div><p>Luke:</p>
<p>I finally succeeded in getting KA to upload the key to
pool.sks-keyservers.net. But KA didn't do it without some
guidance....</p>
<p>Because of your comment,</p>
<blockquote>
<p>(the http:// prefix is important, otherwise hkp is used
again)</p>
</blockquote>
<p>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 "<a>hkp://</a>" protocol specification. The key was
uploaded with no problem.</p>
<p>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.</p>
<p>-Jess</p></div>Jess W. Driskelltag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-26T19:01:51Z2012-09-26T19:01:51Z"Send Keys Failed! Code=0"<div><p>Hi Jess,</p>
<p>unfortunately GPG Keychain Access has a known bug where
sometimes<br>
the communication with keyservers fails.<br>
While it would be a nice explanation, unfortunately I don't think
that's the problem.<br>
As you see in the error you posted before, the protocol is
correctly detected even without the prefix.<br>
So I wonder if this was coincidence.<br>
We'll have to test this thoroughly. Thanks for the hint!</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-28T05:12:52Z2012-09-28T05:12:52Z"Send Keys Failed! Code=0"<div><p>Luke:</p>
<p>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.</p>
<p>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....</p>
<p>In any case, the problem seems to be resolved for me.</p>
<p>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.</p>
<p>-Jess</p></div>Jess W. Driskelltag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-28T15:32:32Z2012-09-28T15:32:32Z"Send Keys Failed! Code=0"<div><p>Yeah, this might be the old bug. We hope to get this fixed soon,
so it finally works reliably and always.<br>
In addition keyservers themselves are not always reliable.</p>
<p>Thanks for the very kind words! It's great to hear when our
users are satisfied :)</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/190516632012-09-28T15:32:49Z2012-09-28T15:32:49Z"Send Keys Failed! Code=0"<div><p>Closing this discussion. Feel free to open a new one
anytime!</p></div>Luke Le