Re:Google says "not a security vulnerability", quickly fixes...
by Eikon on Friday July 04, 2025 @03:32AM
(#44462065)
I think "critical" is due to the context, it's supposed to be trusted software that participates in the trusted public key infrastructure.
If your seed is corrupted, the whole model collapses. There's not a ton of diversity in CT implementations.
Personally, I think usability issues can have security implications. Taken to the extreme, look at RSA: technically possible to use securely, but widely considered insecure because everybody screws it up. Modern crypto libraries are all about achieving better security by fixing footguns. This issue isn’t RSA, but I bet fully fixing this issue would make a small but tangible number of insecure users secure. I think Google should have a clear and spelled out policy re usability issues with security implications, and should give this guy at least some reward, even if it’s not the “critical vulnerability” he makes it out to be.