| commit | ca65bff67c7bfeb84531be8044ca874db2294c01 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Apr 02 22:38:15 2021 -0400 |
| committer | Adam Langley <agl@google.com> | Thu Apr 08 17:15:22 2021 +0000 |
| tree | 5bd11098fb02e689506597c90ee3e0f1a8a22b64 | |
| parent | c31fb79cfe35f8b14731bb2598d091b2e1394577 [diff] |
runner: Construct finishedHash earlier. We currently construct finishedHash fairly late, after we've resolved HelloRetryRequest. As a result, we need to defer some of the transcript operations across a large chunk of code. This is a remnant of earlier iterations of TLS 1.3, when HelloRetryRequest didn't tell us the cipher suite yet. Now the cipher suite is known earlier and we can construct the finishedHash object immediately. In doing so, move HRR handling inside doTLS13Handshake(). This keeps more of TLS 1.3 bits together and allows us to maintain the HRR bits of the handshake closer to the rest of HRR processing. This will be useful for ECH which complicates this part of the process with an inner and outer ClientHello. Finally, this adds a missing check that the HRR and SH cipher suites match. Change-Id: Iec149eb5c648973325b190f8a0622c9196bf3a29 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/46630 Reviewed-by: Adam Langley <agl@google.com>
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.
Project links:
There are other files in this directory which might be helpful: