Re: [Sks-devel] Inclusion in membership file to peer

2018-01-11 Thread Paul Fontela
Hi, Eric, my data for your membership file is: keyserver.ispfontela.es 11370 # Paul Fontela 0x31743FFC33E746C5 El 09/01/2018 a las 17:56, Eric Germann escribió: > sks-cmh.semperen.com 11370 # > ekgermann@semperen.com0x89ED36B3515A211B639060A9E30D9B9B3EBFF1A1

Re: [Sks-devel] Inclusion in membership file to peer

2018-01-09 Thread Alain Wolf
> Am 09.01.18 um 17:56 schrieb Eric Germann: >> Good morning, >> >> I am looking for peers for a new SKS keyserver installation. >> >> I am running SKS version 1.1.6, on sks-cmh.semperen.com >> >> The server is physically located in Columbus,OH region of AWS >> >> The server _has_ IPv6

Re: [Sks-devel] Inclusion in membership file to peer

2018-01-09 Thread Moritz Wirth
Hi, the pgp keyserver dump is outdated for about 100k keys - i created a new dump which you can use: https://cdn.fstatic.io/sksdump My peering lines: keys.flanga.io 11370 # Flanga SKS Peering Administrator 0xd015c49b2eceb8f1 keys2.flanga.io 11370 # Flanga SKS Peering

[Sks-devel] Inclusion in membership file to peer

2018-01-09 Thread Eric Germann
Good morning, I am looking for peers for a new SKS keyserver installation. I am running SKS version 1.1.6, on sks-cmh.semperen.com The server is physically located in Columbus,OH region of AWS The server _has_ IPv6 connectivity. I have loaded a keydump from pgp.key-server.io, dated