Re:OpenSSL 3.0.7 Published
by hsbauauvhabzb on Thursday November 03, 2022 @06:18AM
(#33449059)
I agree with pretty much everything you said, but possibly a common metadata format (both our separate tools report differently but off the same data, etc).
I also think that you’re probably right we the patched in, it’s not infinitely scalable, but I doubt it needs to be anyway
Introducing a new tool will only add another on top of the existing tools, when nothing tells us that people will use it! (plug the xkcd on n standards -> fix with a better standard -> n +1 standards)
Basically, you want to make everyone use a single tool when humans always strive to build something better or just different :)
The best we could hope to achieve is to have the CVE MITRE database start accepting "patched in" strings from all the distributors (so as Ubuntu pushes a signed and patched package to the archive, it pings the CVE db with a new version string for eg. Ubuntu-22.04 namespace).
Even that gets tricky with dependencies and issues covering multiple packages ("this is only patched if you've updated both of these"), though that's a technically solvable problem.