Fold SSL_CTX_set_grease_sigalgs_enabled into SSL_CTX_set_grease_enabled Absorbs grease_sigalgs_enabled into the general grease_enabled toggle. Increments BORINGSSL_API_VERSION to 44. Update-Note: GREASE for signature_algorithms extensions in ClientHello messages can no longer be controlled independently of other uses of GREASE. Callers of SSL_CTX_set_grease_sigalgs_enabled should now call SSL_CTX_set_grease_enabled. Bug: 526597789 Change-Id: Ia6b354db4d58d2a94d6c9c4dab7acc176a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/104128 Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: David Benjamin <davidben@google.com> Auto-Submit: Lily Chen <chlily@google.com> 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:
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: