4 ms·

BoringSSL is more for client side tbf. It was built for Chromium. It is not recommended to use for general parties, even Google does not recommend.

• rockwotj 4y ago
  It was not built for chromium AFAIK To quote: https://boringssl.googlesource.com/boringssl/ https://boringssl.googlesource.com/boringssl/ BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
• vlovich123 4y ago
  Can you clarify how you came to this conclusion? No idea about self-hosted stuff of course, but I'm pretty sure BoringSSL is one of the gold standards for the big cloud providers. Counterpoints: > Encryption Implemented in the Google Front End for Google Cloud Services and Implemented in the BoringSSL Cryptographic Library https://cloud.google.com/docs/security/encryption-in-transit https://cloud.google.com/docs/security/encryption-in-transit > We use a common cryptographic library, Tink, which includes our FIPS 140-2 validated module (named BoringCrypto) to implement encryption consistently across Google Cloud https://cloud.google.com/docs/security/encryption/default-encryption https://cloud.google.com/docs/security/encryption/default-en... > It may (or may not!) come as surprise, but a few months ago we migrated Cloudflare’s edge SSL connection termination stack to use BoringSSL: Google's crypto and SSL implementation that started as a fork of OpenSSL. https://blog.cloudflare.com/make-ssl-boring-again/ https://blog.cloudflare.com/make-ssl-boring-again/ > We ported our SMTP server to use BoringSSL, Cloudflare’s SSL/TLS implementation of choice https://blog.cloudflare.com/email-routing-leaves-beta/ https://blog.cloudflare.com/email-routing-leaves-beta/ > We are pleased to announce the availability of s2n-quic, an open-source Rust implementation of the QUIC protocol added to our set of AWS encryption open-source libraries. <snip> AWS-LC is a general-purpose cryptographic library maintained by AWS which originated from the Google project BoringSSL. https://aws.amazon.com/blogs/security/introducing-s2n-quic-open-source-protocol-rust/ https://aws.amazon.com/blogs/security/introducing-s2n-quic-o... This last one is not 100% clear but I would imagine AWS dogfoods their own encryption libraries to build their internal cloud stack.
  • nicce 4y ago
    Interesting, thanks for pointing put.