| commit | 86c2e62f7428d1e49b0320ea4706704e5a6aca8a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Sep 20 16:18:00 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 24 00:44:57 2024 +0000 |
| tree | 57efbd52affb3f63ff711111754cf84fe6eedb62 | |
| parent | df091b2df3619badea8b58a46da7b1ffea0fc863 [diff] |
Rearrange 0-RTT key schedule setup slightly We used to sometimes setup the 0-RTTs keys before reverifying the certificate, and sometimes after due to QUIC's needs, which was why the long comment (see https://boringssl-review.googlesource.com/c/boringssl/+/38885). That comment is now inaccurate and we consistently haven't installed 0-RTT keys yet. Update the comment and then avoid splitting up the key setup and the reverify step. This shouldn't have any real consequences, except that adding the dummy ChangeCipherSpec messgae now happens *after* setting hs->early_session, and can potentially even happen after we set in_early_data if we want to. Bug: 42290594 Change-Id: I427c9cd521bd11982be3056a0099150a50dd9558 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71528 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: