sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] Unusual traffic for key 0x69D2EAD9 and 0xB33B4659


From: Shengjing Zhu
Subject: Re: [Sks-devel] Unusual traffic for key 0x69D2EAD9 and 0xB33B4659
Date: Sun, 24 Mar 2019 19:57:38 +0800

On Thu, Mar 21, 2019 at 2:42 AM Andrew Nagy <address@hidden> wrote:
>
> All,
>
> Looking to figure out a solution here. A Maintainer on the Ubuntu Key server 
> informed me about discussion of the following keys 0x69D2EAD9 and 0xB33B4659 
> here: https://lists.nongnu.org/archive/html/sks-devel/2019-01/msg00003.html
>
> Unfortunately the email address address@hidden is just a black hole and so 
> the email that was sent there from Brent Saner was lost forever.
>
> I currently run the FreePBX project which uses the GPG network to sign 
> modules. Unfortunately due to: 
> https://bitbucket.org/skskeyserver/sks-keyserver/issues/57/anyone-can-make-any-pgp-key-unimportable
>
> Someone poisoned our master key that we use to sign all other keys. This has 
> caused issues on the sks network for a while. However since January we've 
> noticed more and more sks servers are now just timing out and not returning 
> back our requests for 0xB33B4659. I assume that is probably because of the 
> message thread from January.
>

Actually I've not blacklist your keys. But these two keys are not only
pulled too frequently, they are tooo large. I assume it's not your
fault, but someone poisons them.

0x1013D73FECAC918A0A25823986CE877469D2EAD9 stored in the key server is 38M.

As to no response for these requests, probably the key servers are just down :(

Please just don't rely on the key server network for such task, you
can use https://wiki.gnupg.org/WKD

-- 
Regards,
Shengjing Zhu



reply via email to

[Prev in Thread] Current Thread [Next in Thread]