-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear all,
As previously discussed on this list, and listed as issue 5 in the
tracker[0], a more dynamic approach to inclusion in the server pool is
favorable to the current approach of difference to a reference
keyserver (currently keys.kfwebs.net).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.04.2012 02:02, Ryan wrote:
I had problems reverse proxying 11371 behind a load balancer; would
break other sks servers fetching keys.
What I ended up doing was configure SKS to use 21371 on external
interface and the proxy on 11371; other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.04.2012 05:23, John Clizbe wrote:
Anyone else seeing this?
On a somewhat related note, a rather interesting configuration is
found on http://88.191.144.226:11371/pks/lookup?op=stats that lists
pool.sks-keyservers.net 11370 as a peer.
- --
-
