commit | 6c3a63970fbaea7b4f1db23f3213b0c52586cc6c | [log] [tgz] |
---|---|---|
author | Nick Harper <nharper@chromium.org> | Wed Aug 28 22:48:35 2024 +0000 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 29 21:05:09 2024 +0000 |
tree | 2b92aee537e788250d4c8aaba1c3d601799ae057 | |
parent | 3a138e43694c381cbd3d35f3237afed5724a67e8 [diff] |
DTLS 1.3 compatibility mode fix in test runner. Compatibility mode is disabled in DTLS 1.3, but https://boringssl-review.googlesource.com/c/boringssl/+/69947 missed a spot where the test runner still sends a ChangeCipherSpec message. Bug: 715 Change-Id: Ia7dda19e99fc427fb1ba18542b6ed6b4281656c0 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70668 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> Auto-Submit: 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: