[Sks-devel] Intent to de-peer: anything less than 1.1.2

[Phil Pennock]

This is a general heads-up, of action I currently intend to take around
the second half of September; I'll individually mail any affected peers
closer to the time.

sks-peer.spodhuis.org runs with an "HA" setup, a reverse-proxy in front
of the service port, to minimize issues caused by slow peers.  This
setup is somewhat incompatible with peers running SKS prior to 1.1.2,
because those old versions use HTTP/0.9 POST requests which can't pass
through a proxy, so peering is not bi-directional and key propagation is
slowed.

Folks running old servers: please don't take this personally, but I
don't really want to continue indefinitely peering with servers that
can't reliably communicate with me.

It's been a while since that fix and by now most servers are running at
least version 1.1.3.  Every keyserver operator is entitled to run
whichever version of the software they want, with whatever local
policies they want.  It's just that I'm going to make sure my system
spends most of its peering time working with peers that are going to
send me keys back.

This page:
 https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering#!sks-versions
concisely lists some major known issues with older versions of SKS;
meanwhile a more complete CHANGELOG of the current code can be found at:
 https://bitbucket.org/skskeyserver/sks-keyserver/src/tip/CHANGELOG?at=default

So, in late September, I will start pruning peers to remove anyone
running 1.1.1 or older.  If you want to stay on old software, that is of
course your right and we'll regretfully just part ways, no longer
peering; should you upgrade SKS later, I'll be happy to re-peer with
anyone I de-peer in this process.

Regards,
-Phil

pgpe3JFg_rLrh.pgp
Description: PGP signature