I read through that too, and immediately thought about the OpenBSD approach: Don&#x27;t create hacks and workarounds in your own code for what bugs and shortcomings which should be fixed upstream. Send a patch to fix it upstream, and you&#x27;ve fixed your project too.<p>Clearly OpenSSL and BoringSSL (but not LibreSSL) lack a defined way to properly and deterministically identify themselves as projects, in a stable fashion. He should try submitting a patches to get each project to expose a unique property which can be detected in consumer-code.<p>That way (like OpenBSD does) he haven&#x27;t just solved the problem for himself, but for other projects too.<p>If more people had that attitude towards code quality which the OpenBSD team has, we might not be in such a buggy universe as we are now.