| commit | 10458977f6a803859808365fad071731369f655a | [log] [tgz] |
|---|---|---|
| author | Nick Harper <nharper@chromium.org> | Wed Oct 26 15:28:08 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 02 18:00:49 2022 +0000 |
| tree | a5c4560371978dd6c1a4b1c90e70675b6f5c6449 | |
| parent | 054a5d36bb4df09f4ecf62f6ddeb2439aa76d4ba [diff] |
Allow using the TLS exporter in more cases. SSL_export_keying_material can only be used when the exporter secret is available, e.g. during False Start (TLS 1.2) and on the server when processing 0-RTT (TLS 1.3). These conditions were special cased, but there is at least one more case in TLS 1.3 where the exporter secret is available. This change switches the logic for TLS 1.3 to check whether the exporter secret has been derived and makes SSL_export_keying_material functional if it has, instead of checking if the handshake is in one of some number of specified states. Allowing the availability of the exporter in TLS 1.3 on the server after processing the client's handshake flight and sending the server Finished is equivalent to the already-allowed case of exposing the exporter in TLS 1.2 False Start. Bug: b:255591447 Change-Id: Ib216fd4a676524a777aae17569161c02dd2e40ca Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/55025 Commit-Queue: David Benjamin <davidben@google.com> Auto-Submit: Nick Harper <nharper@chromium.org> Reviewed-by: 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:
There are other files in this directory which might be helpful: