| commit | 1530333b25589ee4d4d52b10e78ee55dd82f6dcd | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon May 23 17:18:34 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 24 15:22:39 2022 +0000 |
| tree | f2da2118dc1eee93344f0d592d302119dd0ead72 | |
| parent | 71573dc40bea04ee918d186376be0814fe9ce384 [diff] |
Remove X509_CRL_METHOD. This has no callers, and seems to be practically unusable. The only way to set an X509_CRL_METHOD is X509_CRL_set_default_method, which is not thread-safe and globally affects the CRL implementation across the application. The comment says it's to handle large CRLs, so lots of processes don't have to store the same CRL in memory. As far as I can tell, X509_CRL_METHOD cannot be used to help with this. It doesn't swap out storage of the CRL, just signature verification and lookup into it. But by the time we call into X509_CRL_METHOD, the CRL has already been downloaded and the data stored on the X509_CRL structure. (Perhaps this made more sense before the structure was made opaque?) Update-Note: APIs relating to X509_CRL_METHOD are removed. Change-Id: Ia5befa2a0e4f4416c2fb2febecad99fa31c1c6ac Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/52687 Reviewed-by: Adam Langley <agl@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: