How to send a key to a keyserver?
Kristian Fiskerstrand
kristian.fiskerstrand at sumptuouscapital.com
Mon Mar 2 08:43:21 CET 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 03/02/2015 02:45 AM, Helmut Waitzmann wrote:
> Kristian Fiskerstrand <kristian.fiskerstrand at sumptuouscapital.com>
> writes:
>
>> On 02/27/2015 12:57 PM, Philip Jackson wrote:
>>> On 26/02/15 18:15, Helmut Waitzmann wrote:
>>>> I tried
>>>>
>>>> gpg2 --verbose --keyserver hkp://pool.sks-keyservers.net
>>>> --send-keys -- 72ABFF0923A87CF22D0ED7C4FDEE765D017077F1
>>>>
>>>> and got the message
>>>>
>>>> gpg: sending key FDEE765D017077F1 to hkp server
>>>> pool.sks-keyservers.net gpgkeys: HTTP post error 22: The
>>>> requested URL returned error: 417 gpg: keyserver internal
>>>> error gpg: keyserver send failed: Keyserver error
>
>> 417 really shouldn't happen for any of the servers in the pool,
>> as it is explicitly checked that this return code should not be
>> used.
>
>> For 1.4/2.0, please use --keyserver-options debug,verbose to get
>> more information about the interaction from the curl helpers,
>> this will be useful for debugging.
>
..
>
> Ah! gpg is using my http proxy. proxy.zuhause.test is only known
> to my own DNS service, resolving (after following an alias) to IP
> address 192.168.0.1.
>
> Issuing same gpg2-command again, after unsetting the environment
> variable http_proxy:
..
>
> So it's a problem with my http proxy?
>
Anything else would surprise me. A hint is to look for any mismatch
handling of HTTP/1.0 vs HTTP/1.1 with regards to the 100-Expect, you
can find some information on the matter for the keyserver operators at [0]
References:
https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering
- --
- ----------------------------
Kristian Fiskerstrand
Blog: http://blog.sumptuouscapital.com
Twitter: @krifisk
- ----------------------------
Public OpenPGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
- ----------------------------
Aurum est Potestas
Gold is power
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCgAGBQJU9BSUAAoJEP7VAChXwav66pwH/1fZIfNadxa2cEpgvsScQVid
ggaJSfVrNyAye1bFacSjhMBxL61G7jVuGQkvOq+l1WNOYNzwP2ZsjQJ7XpaCP0IM
bE1omqNwYM5GNk4eA1PTjxJjoX1O2l8+umzIOZ7lMOWnB8YsqziIwPz36RCVGQ15
cYzK9G+Ca7uCmyQ09dYnY7MvfN+U49SoSPz3PJJgGKD+9nuStSphaY7Bu8kWqXOm
JyW4BgPThQvhLjqOIStbPIvFRC9BTSibRiCI5Bc3NMljYC/RFuXzmDyveVbf9jjc
fN/X5tn0Ygax3AKZryGYynjOiDA+tQuazf+LzqZ0apHT+guEF1vW6zkS8xWN1s4=
=mr9o
-----END PGP SIGNATURE-----
More information about the Gnupg-users
mailing list