From 54be7bca13f59cf326413153c21e795e4d9742ff Mon Sep 17 00:00:00 2001 From: Rohan Kumar Date: Mon, 24 Apr 2023 09:53:04 -0700 Subject: [PATCH] Add more boringssl users --- content/notes/using-boringssl.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/notes/using-boringssl.md b/content/notes/using-boringssl.md index 88a7e8a..97ea648 100644 --- a/content/notes/using-boringssl.md +++ b/content/notes/using-boringssl.md @@ -6,6 +6,11 @@ replyTitle: "“BoringSSL…is not intended for general use”" replyType: "Comment" replyAuthor: "AJ Jordan" replyAuthorURI: "https://strugee.net/" +syndicatedCopies: + - title: 'The Fediverse' + url: 'https://pleroma.envs.net/notice/AUjf1wCr0xk0yCVpKK' + - title: 'Lobsters' + url: 'https://lobste.rs/s/9eas9d/you_should_prepare_for_openssl_3_x_secvuln#c_lreowa' --- Despite BoringSSL's "not intended for general use" warning, it's used by many projects: @@ -14,5 +19,7 @@ Despite BoringSSL's "not intended for general use" warning, it's used by many pr - Cloudflare: used everywhere, including Quiche. - Apple's Secure Transport (it's in both major mobile OSes!) - Optionally: Nginx, libcurl +- (Update ) [Apple's SwiftNIO SSL](https://github.com/apple/swift-nio-ssl) +- (Update ) [AWS libcrypto](https://github.com/aws/aws-lc) is based on BoringSSL I use nginx-quic with BoringSSL without issue, although I did have to use [a separate script](https://github.com/tomwassenberg/certbot-ocsp-fetcher) to manage the OCSP cache. The script manages the cache better than Nginx ever did, so I recommend it; it should be trivial to switch it from OpenSSL to LibreSSL.