Re: [Sks-devel] pool.sks-keyservers.net issues

[Phil Pennock]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

[ trimmed CC list, dropped gnupg-users & people not directly relevant to
  this post ]

On 2013-03-01 at 00:46 -0800, Doug Barton wrote:
> Wow, what a thorough analysis, thanks Phil. :)  FWIW, I did see those
> Expect: headers you describe in my debug output, and obviously if this
> issue only affects certain servers it would explain why I was only
> seeing it intermittently.
> 
> I should have added before, I'm on Ubuntu 12.10, and gpg2 comes built
> with libcurl.

For now, find a local keyserver you can reach, with low latency, confirm
you can --send-key to it, and use that server's hostname as your
keyserver, instead of a pool.

  http://www.sks-keyservers.net/status/

and the much uglier:
  http://sks.spodhuis.org/sks-peers
which says more about which proxy software might be running and will let
you filter for nginx.  For you, right now, you might want to constrain
to an nginx server.

Kristian: might it be worth nginx.ha.pool.sks-keyservers.net and
apache.ha.pool.sks-keyservers.net or is that a step too far?

Also: perhaps the colour boxes in the RProx column, when green, might be
overlaid with an 'N' or an 'A' to help quickly tell them apart?

I might be horribly wrong.  After all, if I were any good at web design,
the spodhuis site wouldn't suck so much.  ;)

- -Phil
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlEwc78ACgkQQDBDFTkDY3/XfQCfTXQ+25lUKvtmZ6l6aEPWUFL5
n5gAnRSXg/hyGUGWPw0FwLbAxaHIvJo8
=txpN
-----END PGP SIGNATURE-----