| commit | 74bab4cf7b9c7c2fd9c37b3eecfa059f1ffc218a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Dec 25 16:51:37 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 10 20:49:23 2024 +0000 |
| tree | eacac60b8276442ebcc25f0b649ce42b85e032ae | |
| parent | 0beff26c59e67e2e19d173f1bd23241a0e946fd9 [diff] |
Remove X509_TRUST_OCSP_SIGN and X509_TRUST_OCSP_REQUEST These are unused and are the only options that remove the "compat" self-signed fallback. X509_TRUST_OCSP_REQUEST was intended for checking signed OCSP requests. While OpenSSL's OCSP implementation (which we've dropped) does attempt to configure it, it actually does nothing. They call X509_STORE_CTX_set_trust after X509_STORE_CTX_set_purpose, but X509_STORE_CTX_set_purpose already sets the trust parameter and X509_STORE_CTX_set_trust only acts when trust is not configured. X509_TRUST_OCSP_SIGN was briefly used in upstream's 30c278aa6bb614f4cfc5a26c7cbe66ad090f6896, by way of X509_PURPOSE_OCSP_HELPER, but then immediately undone in e9754726d236b74476cd0be5fa60acfef0c7024f. Change-Id: I6d2cf9b88a6b013e74fe95cd88f94051111086df Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65151 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: 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: