upvote
> boringssl

"Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability." (Their README).

> LibreSSL

That does indeed still seem like the most promising avenue. But it is "just" a fork of OpenSSL.

> rustls

It relies on one of two crates for cryptographic primitives, both of which have zero regard for long term support. "Latest release or bust" doesn't cut it for crypto.

reply
You do need to keep TLS up to date as the network changes around you. Just recently you needed to block eMudhra intermediate certificates.
reply
> You do need to keep TLS up to date as the network changes around you.

Yes. Which is precisely why you need cryptographic libraries that take long term support seriously and don't just fix whatever the latest version is.

> Just recently you needed to block eMudhra intermediate certificates.

Why on earth is your TLS library responsible for your CA certificate database?!

reply
Because it's a TLS feature? That's what people want from TLS libraries? They say connect, and if it succeeds it's secure?
reply
But the database of trusted CAs is kept and maintained independently of the TLS library, obviously! It's data, not code. And it's agnostic as to which library uses it.

Any comments on my clarification about your misunderstanding of long term support?

reply