| commit | 4c647a5623c3da9bfa8f9cd7d4f60c992b0685c3 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Nov 27 18:16:51 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 06 22:59:14 2024 +0000 |
| tree | ede651962c30a9df35e52f075a3b6aed7323ef50 | |
| parent | bbf03ea966c726dee05769cb3c499d78c4eb2311 [diff] |
Implement the downgrade protection signal in DTLS 1.3 This was originally looking for the client to specifically support the final TLS 1.3 version 0x0304. This has a side effect of not picking up DTLS 1.3, which has a different codepoint. We did it this way because, early in TLS 1.3's development, we had draft versions of TLS 1.3 flying around, and only the final TLS 1.3 can safely ship enforcing this check. Those draft versions are now gone, and this check is now getting in the way of DTLS 1.3. Switch it to checking hs->max_version. Bug: 42290594 Change-Id: Ic2d143af965b4b8bafef524f3f0e85cc3efa42fe Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73728 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Nick Harper <nharper@chromium.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.
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: