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

[Daniel Huigens <[e-mail]>]

Just to get back to the original question; I wanted to ask the
implementations that don't do this check (GnuPG and Sequoia), whether
there are any particular reasons for that? 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?

And then, in the case that we can't solve this for v4, let's at least
try to prevent this from happening again with v5 keys. E.g., we could:

1. Write in the spec that implementations SHOULD do this check for v5
   signatures, or
2. Remove the two hash bytes (and thus the check, obviously) from
   v5 signatures

I'd be happy to make MRs for these, if it's useful, but I guess these
are simple enough that we can discuss them here. I slightly prefer
option 2, while Justus didn't like option 2, I think. Any other
opinions? :)

Best,
Daniel