As a final note we’d like to thank the BoringSSL developers for the great work they poured into the project and for the help they provided us along the way.
Seems like they are working pretty close together and got something out of the deal as well.
Because after Heartbleed we started to look for a performant alternative to OpenSSL that we felt would be safe for us to use.
But why not LibreSSL?
LibreSSL doesn't provide the features of BoringSSL that we use so would have required a huge amount of work to use.
Interesting, I would think it would be easier to use LibreSSL for this since the OpenBSD folks are so conservative that the modern APIs are likely to be stable. Maybe they want to use more of the legacy APIs that the OpenBSD folks are excising?
https://boringssl.googlesource.com/boringssl/
> BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
> 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.