commit | 7fa0910a6511895119a4aa3f474920594e734564 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Thu Jan 26 13:17:18 2023 -0500 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 24 14:45:09 2023 +0000 |
tree | fb497efae28c39fce952d1f7023cb325e1eb4ddd | |
parent | 6ab4f0ae7f2db96d240eb61a5a8b4724e5a09b2f [diff] |
Create the SSLKeyShare object in TLS 1.2 client ECDHE slightly later We call Accept as a TLS 1.2 client and a TLS 1.3 server. In the latter, we create an SSLKeyShare object, Accept, and immediately destroy it. In the former, we create the SSLKeyShare object a couple steps before actually using it. It's equivalent to create the object just before Accept, so switch to that. This change means that hs->key_shares now only ever contains objects in between Offer and Finish. Or, in KEM terms, it only ever contains KEM private keys. (SSLKeyShare objects are currently a little confused about what kind of state they contain.) Change-Id: Idec62ac298785f784485bc9065f7647034d2a607 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/57605 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: