| commit | f86149982323e57050f853c278ce8aa955b681dc | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Nov 12 13:43:33 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Nov 17 16:46:53 2023 +0000 |
| tree | 04f64db0bfd2d02bd32d38a9bbfc7492f551f8be | |
| parent | 1b7fdbd9101dedc3e0aa3fcf4ff74eacddb34ecc [diff] |
Remove delta and extended CRL support Update-Note: The X509_V_FLAG_EXTENDED_CRL_SUPPORT and X509_V_FLAG_USE_DELTAS flags now cause verification to fail. They weren't enabled by any caller. This broadly is meant to disable: - Delta CRLs - Indirect CRLs (When the CRL's issuer is somehow different from the certificate. The security properties for this is very interesting, since it refers to just any other random name under the same trust anchor. Very clearly a remnant of when X.509 was meant to authenticate a global directory. See the rather worrisome comment over check_crl_chain.) - Merging together multiple CRLs that are partitioned by reasons There's some other code we can now unwind, which will be handled in follow-up changes. This CL is meant to be a minimal change to disable them. Though even this minimal change requires we delete a bunch of functions. Bug: 601 Change-Id: I319ab793f480c6b99de86da6077b616f18edf06b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/63929 Reviewed-by: Bob Beck <bbe@google.com> Auto-Submit: David Benjamin <davidben@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: