[Sks-devel] Shutdown of pgp.ustc.edu.cn

2019-07-02 Thread Shengjing Zhu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I have shutdown pgp.ustc.edu.cn. Please remove this server from your membership file. Thanks! Shengjing Zhu -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAl0bfEwACgkQONAPABi+ PjWY5Af/TgKjHnl1KKhKeHNH8ZEc2nBoMqxH7Ob

Re: [Sks-devel] new attack on sks keyserver ?

2019-07-02 Thread stuff
Hi Alex, Your correct, sks does not have a future as no one is maintaining them and as you have seen they can no longer fullfil their intended purpose. Yakamo On Tue, 2 Jul 2019 07:31:17 -0700 (MST) compuguy wrote: > Robert, > > I think the question that people want answered is does the sks

Re: [Sks-devel] new attack on sks keyserver ?

2019-07-02 Thread compuguy
Robert, I think the question that people want answered is does the sks keyserver network have a future? Based on what I've been reading as far back as 2018, seems to indicate that servers like keys.openpgp.org are the future. Thank You, Alex "compuguy" Hall Robert J. Hansen-3 wrote >> https://

Re: [Sks-devel] new attack on sks keyserver ?

2019-07-02 Thread info
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Stop serving poisoned certificates to any client (by configuring our HTTP gateway with another URL blacklist, so that GETs for poisoned keys are not allowed). I'm planning to use some of the existing DB statistics scripts to extract

Re: [Sks-devel] new attack on sks keyserver ?

2019-07-02 Thread me
Hi Jorge, you might as well use keys.openpgp.org in that case. you wont have to maintain broken software or deal with piosoned keys. or you can even run your own instance of Hagrid if you want to maintain control. Yakamo On Tue, 2 Jul 2019 12:16:24 +0200 Jorge Gonzalez wrote: > Hi, all,

Re: [Sks-devel] new attack on sks keyserver ?

2019-07-02 Thread Jorge Gonzalez
Hi, all, just in case anyone is interested, these are the first measures that I have implemented (or plan to implement) on ICIJ key server: * Stop accepting SKS updates from peers (by removing all peers from our "membership" file). - DONE * Stop accepting SKS updates from external sources (by co