upvote
We used BoringSSL at Cloudflare. I imagine there’s a lot of usage in places you can’t see despite it not seeing more adoption. One place you can see it is all browsers use it since Chromium bundles it everywhere except Apple but Apple’s OSes use it to underpin their Network.framework which underpins WkWebview so all Apple devices use it.
reply
Seriously, at this point BoringSSL is surely more widely deployed than OpenSSL? A billion Apple devices, plus every Chrome installation?
reply
> all browsers use it since Chromium bundles it

Doesn't Firefox use NSS instead?

reply
BoringSSL is somewhat widely used because Google baked it into their projects (and partially by Microsoft, I believe they made a FIPS variant of it and used it in Go?)

LibreSSL had, IIRC, problem known as OpenBSD-itis. Or to put it bluntly, the developers didn't really care about any other platform. Plus I will admit that being the first and loud "we will fix openssl" they got linked with some loud PR that showed less understanding of code they mocked than OpenSSL developer who wrote it, and that's really impressive when you consider some of the mocked code fragments were results of developers never reading foundational documentation for a platform

reply
> LibreSSL had, IIRC, problem known as OpenBSD-itis. Or to put it bluntly, the developers didn't really care about any other platform.

Well put. This is the crux of the issue.

If you ever try to use libreSSL you rub up against so much friction that most projects would hammer out early.

reply
There's LibreSSL portable. It worked better in legacy machines I own, go figure.
reply