|author||David Benjamin <firstname.lastname@example.org>||Sun Feb 09 16:28:52 2020 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Feb 13 19:57:57 2020 +0000|
Clean up TLS 1.3 handback logic. There's no need to treat the 1-RTT and 0-RTT handback flows differently. This aligns the 1-RTT handback with the 0-RTT point. This consistently installs the decryption keys in the state machine after handback rather than while applying the handback. Update-Note: This changes the serialization format for TLS 1.3 split handshakes, which were only just added. Change-Id: I0e109cb8d9ecd3c8658dfa26059cbe0139f82eed Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39988 Commit-Queue: David Benjamin <email@example.com> Reviewed-by: Matt Braithwaite <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: