Re:OpenSSL 3.0 released; relicensed to Apache-2.0
by nemothekid on Monday September 20, 2021 @06:04PM
(#28599617)
>Google gave us HTTP/2/3, but don't seem to care about fixing TLS.
Google is working on BoringSSL / Tink, which I believe is API compatible, but supports a lot less features. However I think a better way forward might be RustTLS, an implementation which is memory-safe. There is already support in Curl[1], showing there is a path forward for usage in languages other than Rust.
Google is working on BoringSSL / Tink, which I believe is API compatible, but supports a lot less features. However I think a better way forward might be RustTLS, an implementation which is memory-safe. There is already support in Curl[1], showing there is a path forward for usage in languages other than Rust.
[1] https://daniel.haxx.se/blog/2021/02/09/curl-supports-rustls/