Re: [openpgp] Expected client behaviour ambiguity in signature verification

[Andrew Gallagher <[e-mail]>]

On 15 Jul 2022, at 15:25, Daniel Huigens <d.huigens=[e-mail]> wrote:
> 
> Are there many keys out
> there that fail this check? I understood that GitHub has one, generated
> using OpenPGP.php, would it be possible to ask them to generate a new
> key, or modify their existing one? (Someone could do that for them, I
> guess :)) Or are there too many keys like this out there?

I hotpatched hockeypuck to log this particular error against a primary key identifier and loaded an SKS dump. It has only been running a few minutes but it is already at several hundred unique primary keys affected, and counting at ~ 50 keys per batch of 15000. Scaling that up gives a ballpark of 22,000 keys in the full SKS dataset with bad hashtag self-signatures.

This does seem to be a surprisingly large number. Beware though that “affected” and “broken” are not the same thing - keys with bad self-sigs may have later, valid self-sigs on the same UIDs, and distinguishing these would require a more sophisticated test. But if GitHub still haven’t fixed their key, what are the chances that others have?

A