Page MenuHome GnuPG

gpg should try to connect using HTTP if HKP fails
Closed, ResolvedPublic


It is something really common to not be able to use gpg from behind a corporate firewall (where very few ports/protocols are allowed).

Instead of having to patch thousands of scripts that are trying to connect to keyervers to use HTTP it would be much wiser to have the HTTP
connection method as a fallback.

Current usage example:

gpg --send-keys --keyserver $key

result> fails

Current workaround:
gpg --send-keys --keyserver hkp:// $key

Proposed behavior: to try to connect using port 80 if there is no response in x seconds when connecting to HKP port.

PS. This is not specific to "send-keys", the same does apply for getting them.

Event Timeline

werner lowered the priority of this task from Normal to Wishlist.May 24 2011, 9:01 AM
werner added a project: Feature Request.
werner removed a project: Bug Report.
werner claimed this task.

There are keyservers which listen on port 80 or 443. They can be used in such
cases. See