|author||David Benjamin <firstname.lastname@example.org>||Fri Apr 02 23:11:19 2021 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Apr 06 18:13:31 2021 +0000|
runner: Don't use the buffer in TLS 1.3. All the comments say the buffer is only needed in TLS 1.2, but this doesn't match the code. The code uses the buffer in one place, for ECH, to avoid copying a hash.Hash. Go does support this, albeit in a *very* roundabout way. This is ugly but means we can now properly drop the handshake buffer in TLS 1.3. Change-Id: I4a1559a64fcb98ccfbab54de99402fe6f62725a1 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/46627 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: David Benjamin <firstname.lastname@example.org>
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.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
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.
There are other files in this directory which might be helpful: