| commit | 832242f75782acbe23c5850c025c5eb399a5f725 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Nov 04 15:40:39 2024 +0000 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 14 21:29:52 2024 +0000 |
| tree | 8c2a846233d48a518da743422b7c3a5bee572a9a | |
| parent | 42b96b62d51a18e8867f92034a50e74ac2000fab [diff] |
Better track final vs early versions https://boringssl-review.googlesource.com/c/boringssl/+/71534 generally made things cleaner, but lost a subtlety: when we check if the version is set, sometimes we care about whether it is an early version or final version. This includes the two minor behavior changes listed there, and a host of TODOs we kept adding to the DTLS 1.3 implementation. We don't yet implement DTLS 1.3 0-RTT, but let's just resolve these TODOs now rather than constantly having to make a note of this. Bug: 42290594 Change-Id: I74e1367836762a6e6fd8d216158ee5309d387cce Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72887 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: