SKS and GnuPG related issues and possible workarounds

Ryan McGinnis ryan at
Sun Jul 7 01:15:45 CEST 2019

I believe this list is web accessible to non-subscribers, so being subscribed here or not subscribed here doesn’t mean much.  Just that if you post here someone who is willing to do this attack (maybe not even the original someone - this is an attack literally anyone can do) is reading what you write.

*waves at someone*

At any rate, this just underscores what I suspect the original attacker was trying to make clear: stick a fork in SKS servers, they’re dead.

-Ryan McGinnis
PGP: 5C73 8727 EE58 786A 777C 4F1D B5AA 3FA3 486E D7AD
Sent with ProtonMail

On Sat, Jul 6, 2019 at 17:18, David <david at> wrote:

> On 06/07/2019 12:50, Ryan McGinnis via Gnupg-users wrote:
>> Someone brought it to my attention that my key is now one of the
>> affected keys; I think from this we can probably surmise that whoever(s)
>> is doing this probably reads this list as this email address doesn’t see
>> heavy circulation.
> If in deed that's the case - that person can download any public key
> insert malicious code and upload to any key server. I am not updating
> any keys and no sks key servers.
> Who's new to the mailing list? Now we have a web of distrust :(
> David
> --
> People Should Not Be Afraid Of Their Government - Their Government
> Should Be Afraid Of The People - When Injustice Becomes Law, REBELLION
> Becomes A DUTY! Join the Rebellion Today!
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: publicKey - ryan at - 5c738727ee58786a777c4f1db5aa3fa3486ed7ad.asc
URL: <>

More information about the Gnupg-users mailing list