Request to add port number to --send-key and --recv-key output

Kristian Fiskerstrand kristian.fiskerstrand at sumptuouscapital.com
Sun Jan 11 14:57:04 CET 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 01/11/2015 01:11 AM, Daniel Roesler wrote:
> Howdy all,
> 
> Previously discussed on moderncrypto[1], I'd like to request that
> output for --send-key and --recv-key contain the port number for
> keys.gnupg.net. Many of the servers in the sks pool don't mirror
> the keyserver interface on port 80[2], so if you copy and paste
> keys.gnupg.net in a browser, sometimes you see a random site (which
> confused and worried me until I figured it out). If the port
> number were include, copying and pasting into a browser would have
> resulted in the normal sks keyserver HTTP interface.

There are no requirements for the keyservers to present a "human
readable" UI. Ok, so I'm putting that in quotes here since it is all
text based and indeed human readable, but the point is that they would
have to know the HKP specs to perform the lookups using the correct
"API calls".

> 
> Here's the requested change:
> 
> From: $ gpg --recv-key "72EFEE3D" gpg: requesting key 72EFEE3D from
> hkp server keys.gnupg.net

HKP defaults to 11371 so that information is already included by the
absence of anything else.

- -- 
- ----------------------------
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
- ----------------------------
"A government that robs Peter to pay Paul can always depend on the
support of Paul."
(George Bernard Shaw)
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJUsoEuAAoJEPw7F94F4TagPfQP/AylYrE+ZPFESNKkxFtNGUpV
lyxOWjlcZnnm4VDq2pZAkb8ibkEJFCzARYlS/LOzj6x/71nRdAaKav2DMxxl7GD5
oK56q8+4HcUj3fU/GRFos0UAoxgqI2gfy4svOM/3eUtneJrr5iIIyDnZJxNDrbHX
K0FLtLU5ALmap90PG+qlL2N3hweO+hE1smBDF4YP6QpGw7r668cjdRAeCjuHhFIw
AaPDuGotIMO9SO2Hh+J0+RGLSOQJz3JLDQDgy5J61uhzxURLVBHzyqqeYZ0/nBx3
5HVX/tsI7SaatYyIhrtiSa0I03gXf0NvhT1UdU/DS8StqmNT5R2jCeQmnoKHklgz
CcGQWMHmV1t+AwhFw+cSJG5+VG7umh9ExB9ngAQU8aEf6N2016icWGYn1cc8hCBK
AkvQ50RtZUkHi2viXY2kHwT7QktuVrCvNgPBN/FJvJf50zHdL8tpvPJyHKRph3LX
wv3j+wmeZigVobFHHAmMjEVLisdo0TWsqFloue83GUL9h+BeUvym1vbm+DJwEssl
SD28ZzrSwV92ELwk1+A9vldt1g1Ww/y+FCwp3OFpBHV4n+8Yco5cF5vrabzDmQEX
Qeb2PzuBh9bjjiqnq1pOwpOwjZ6HsDvfsvhbub4dw/dS6jdaIBdELZZGRUpsCMPt
wF5fnscMf6nG1EPhjWPQ
=MB5G
-----END PGP SIGNATURE-----



More information about the Gnupg-devel mailing list