-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 11/05/2012 11:12 AM, Kristian Fiskerstrand wrote: > On 11/05/2012 04:04 PM, Daniel Kahn Gillmor wrote: >> On 11/04/2012 10:46 PM, Casey Marshall wrote: >>> I’d like to share Hockeypuck, an OpenPGP Keyserver I’ve >>> developed in Go (http://golang.org). >> Cool, i'm glad to hear of it. Does this sync with any of the >> existing SKS network? I saw no mention of peer synchronization >> in the README or the project page. >> >> --dkg > > > Indeed interesting to hear of new keyserver implementations, and > having a less homogeneous system should only be beneficial to the > overall security. > > Re SKS sync, this seems to be filed as a RFE/bug already at [0]. > Does it currently sync through the old PKS system / email? >
Not yet, but soon. PKS syncing is an easier stop-gap measure while I study set reconciliation. > Another RFE seems to be RFC6637 support - as the keyserver at the > moment seems unable to accept my key [1]. In addition, if you want > the keyserver to be included in the pool[2] I'd request a > /pks/lookup?op=stats implementation similar to SKS (and indeed > GnuKS[3], that is implemented with a Software: header) > All excellent suggestions, opened in Launchpad. Thanks for the feedback! > Looking forwards to seeing how this keyserver evolves :) > > [0] https://bugs.launchpad.net/hockeypuck/+bug/1044767 [1] > https://keys2.kfwebs.net/pks/lookup?op=vindex&search=0x43FE956C542CA00B > > > [2] https://sks-keyservers.net/status/ > [3] http://key-server.org:11371/pks/lookup?op=stats > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlCYogYACgkQ95Ni2kSi0dspLAD9Ef0VUmUNBLSiPwudn/yhT0YF ZpsQ2XZtQd/mRmls6zkA/2X9h6Gpto+/+CCcPDiFrsHBBBM61NzWnSELJciH5eOs =T3rb -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
