On Tue, 5 Jun 2018, Phil Pennock wrote:
> https://bitbucket.org/skskeyserver/sks-keyserver/wiki/TLS%20Configuration
>
> I've updated it to be clearer about the need for manual action to join
> the pool and to link to the instructions for doing so.
| In practice, there's one well-run HKPS pool,
On 2018-06-05 at 02:53 +0200, Paul Neuwirth wrote:
> my keyserver keyserver.swabian.net has also hkps enabled on port=20
> 443 since several months now.
> But in the pool status page I do not see hkps enabled.
> Do I miss a DNS entry? or is something different wrong with my setup?
This is a pool containing only servers available using hkps. Regular A
and and SRV records are included for port 443 servers, and a lookup
is performed for _pgpkey-https._tcp on the individual servers to
determine if a hkps enabled service is listening on another port. At
this point, however,
This is an OpenPGP/MIME signed message (RFC2440, RFC3156).
--=_MIME_CONTENT_BREAK_=_ESYVDRXTTLZGFRUADUKXAUICTLNKCYC_=
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline; filename="message.txt"
Content-Transfer-Encoding: quoted-printable
Hello,
my keyserver
