| commit | 19ec2a1a54000bc32cd1a8483c5b7dfa0df9c75a | [log] [tgz] |
|---|---|---|
| author | Lily Chen <chlily@google.com> | Thu Oct 02 14:40:59 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 02 11:55:37 2025 -0700 |
| tree | acc51487e6d64278dd2fb1974ebab05300d7e7df | |
| parent | caf5961d5a28df7a18274b932ddfb7fe2272c2dd [diff] |
Add API for caller to hint server's preferred key shares This change introduces a new mechanism for clients to provide a "hint" about which key exchange groups the server is likely to support. This is meant to be used for draft-ietf-tls-key-share-prediction. We will try to make a prediction based on the server's hint, and if a group was predicted, it is sent as the key_share, overriding any explicit key shares configured by the caller. Bug: 437414371 Change-Id: Ie98d2a63e5bfb4f10683ca4f1f77e5439b39e256 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81588 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: