gpgkeys sendKeys using curl does not succeed in Keychain Access
Reported by C Fraire | March 21st, 2012 @ 03:52 AM | in 2.0.19 (closed)
I see a few users having problems with sending to a keyserver in GPG Keychain Access:
http://support.gpgtools.org/discussions/everything/1106-cant-send-t...
http://support.gpgtools.org/discussions/everything/1124-multiple-pr...
I confirm that there is a problem, but I'm not sure why.
The MacGPG2 release at http://www.gpgtools.org/macgpg2/index.html is version 2.0.17-9. Its gpgkeys programs are compiled to use "curl version = libcurl/7.21.4 OpenSSL/0.9.8r zlib/1.2.5".
GPG Keychain Access running a --send-keys with this MacGPG2 is seeing the following error (edited from a run using keyserver-options with verbose,verbose,verbose,debug):
* Failed writing body (0 != 126)
* Failed writing data
gpg: keyserver internal error
gpg: keyserver send failed: Keyserver error
But running the identical --send-keys from the Terminal runs fine without error. I'm stumped on this.
After failing to find a cause, as a last resort, I tried MacGPG2-2.0.18-4+1.dmg from the MacGPG2 downloads page. That version's gpgkeys programs are not compiled to use curl; they use instead "GnuPG curl-shim". With it, there is no problem, and sendKeys succeeds in both GPG Keychain Access and from the Terminal.
Comments and changes to this ticket
-
Clint March 22nd, 2012 @ 05:46 PM
Some further details that may or may not be helpful:
I also saw this problem (1.0b7, installed from the web-published package), and went into the preferences and saw there was no server listed. I added a server, but still got the error. Then I checked the GPGPreferences Pane, and it had a keyserver listed, but the server was different from the one I had entered into the GPG Keychain Access Preferences. So I changed the keyserver in the GPGPreferences Pane, and it worked after that.
I don't know that what I did was the correct thing to do, but I thought I'd let you know that it worked for me.
-
Alex (via GPGTools) March 23rd, 2012 @ 12:00 AM
- State changed from “new” to “open”
-
-
-
-
-
-
-
-
steve April 9th, 2012 @ 04:30 PM
- State changed from “open” to “waiting”
- Milestone changed from “2.0.18” to “2.0.19”
- Importance changed from “” to “High”
Hey Clint,
We have had two issues lately related to key serves. Both have been fixed. So please give the latest nightly version another try from here: http://nightly.gpgtools.org/
Let us know if your problem persists. Should be fixed with the nightly.
Hope this helps :)
steve -
-
steve June 18th, 2015 @ 04:43 PM
- State changed from “fixed” to “released”
- Importance cleared.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
C Fraire
steve