| commit | 5a94aff9aebcf9738c7bc464bc95fa4ac3a46ed7 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Sep 23 16:36:25 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 24 20:20:53 2024 +0000 |
| tree | 3de69140b0af05ea4d6badf8209b1c0ee89383e9 | |
| parent | 15b580f7f6cdfc9626bba4a785a9783faf637e06 [diff] |
Check for 0-RTT vs final version mismatches earlier This makes no immediate difference, but it avoids having two versions' worth of record layers active at once if TLS 1.4 exists later. Right now our record vs connection state is precariously set up to support this because we won't actually shut off 0-RTT until we get to EncryptedExtensions. Checking this earlier means that there is only ever one version's worth of record layer active at once. The cost is that, if TLS 1.4 exists later, we'll need to add a ssl_hs_early_data_rejected point in there. (But we probably will want to anyway if we ever do DTLS 1.3 0-RTT.) Change-Id: I4a626c87caa123de3579c65e0129f385e290024f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71533 Reviewed-by: Nick Harper <nharper@chromium.org> Commit-Queue: David Benjamin <davidben@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: