| commit | b28a8c960b2f1e32f495d7f2850fadd8a55e7f06 | [log] [tgz] |
|---|---|---|
| author | Lily Chen <chlily@google.com> | Tue Sep 09 17:47:29 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 09 15:14:27 2025 -0700 |
| tree | d686c52335789d544e62337cb44399b491e1959a | |
| parent | 0459431a2073a7220bb6fb9303d28680cc87aa68 [diff] |
Allow SSL_HANDSHAKE::key_shares to vary in size This refactors hs->key_shares to a vector rather than a fixed array of size 2. There is at most a key share for every implemented NamedGroup, so the size is capped at the number of named groups. This is needed for allowing the caller to explicitly specify client key shares. There's no behavior change intended in this CL. We still use at most 2 key shares (by default; that will change in the next CL). Change-Id: I0eeb218c59ec1f0e8e062aeb5f833102c40d7bf6 Bug: 437414371 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81487 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: Lily Chen <chlily@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: