-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 You can peer with me. Just use the following line in your SKS membership file:
keyserver.brian.minton.name 11370 # Brian Minton <[email protected]> 0xDBF6A5BA777DF487 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEAREDAAYFAlQy2FgACgkQ2/alund99Ife1wCfYOzBxH4pycyYOGK9Ac93n9r+ KPIAn2qlqdcUKcfEGRWC+aP09ki09O5T =H3QL -----END PGP SIGNATURE----- On Sun, Oct 5, 2014 at 12:01 PM, Pete Stephenson <[email protected]> wrote: > On Sun, Oct 5, 2014 at 5:09 PM, Patrik Kernstock <[email protected]> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> Hello, >> >> I've set up a new keyserver and so I am searching for new peers - I've >> already imported a big keydump. If someone wants to peer with my keyserver, >> please drop me short mail. Thanks! >> The keyserver is available under both: HTTP and HTTPS under the following >> link: https://keyserver.pkern.at/pks/lookup?op=stats > > I've added your server as a peer. To do the reverse, add the following > line to your SKS membership file: > > ams.sks.heypete.com 11370 # Pete Stephenson <[email protected]> 0x85EB9F44 > >> At least I have some questions left: What is exactly HKPS? How to enable it? >> Is this just normal HTTPS? > > Yes. HKP is a subset of HTTP, and HKPS is just HTTPS. However, in > order for an HTTPS/HKPS server to be part of the SKS keyserver pool, > you'll need to submit a CSR to Kristian Fiskerstrand, who will sign it > with the SKS pool CA (a server using a cert signed from a commercial > CA won't be included in the pool). > > Cheers! > -Pete > > -- > Pete Stephenson > > _______________________________________________ > Sks-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/sks-devel _______________________________________________ Sks-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/sks-devel
