keyserver scheme http broken?

Bernhard Reiter bernhard at
Fri Nov 13 09:40:14 CET 2009

Am Freitag, 13. November 2009 05:12:30 schrieb David Shaw:
> Some keyservers run hkp over port 80 to deal with firewalls (so it's  
> hkp:// in those cases).  

Is there a list of those, similiar to or

> I'll take a look at gpg.texi and see if I can make this a bit clearer.

That would be wonderful.
If you are at it: I belive the "scheme" part of the example in the --keyserver 
option should marked as optional. It should be said which the default is then 
(probably hkp). I've noticed because "--keyserver" just works 
and it probably uses hkp. :)


Managing Director - Owner:       (Free Software Company)
Germany Coordinator: Coordinator:
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20091113/e9bffb71/attachment.pgp>

More information about the Gnupg-devel mailing list