|author||David Benjamin <firstname.lastname@example.org>||Mon May 14 18:10:24 2018 -0400|
|committer||David Benjamin <email@example.com>||Tue May 15 23:36:08 2018 +0000|
Restore some revocation-related X.509 extensions. These are tied to OPENSSL_NO_OCSP in upstream but do not actually depend on most of the OCSP machinery. The CRL invdate extension, in particular, isn't associated with OCSP at all. cryptography.io gets upset if these two extensions aren't parseable, and they're tiny. I do not believe this actually affects anything beyond functions like X509_get_ext_d2i. In particular, the list of NIDs for the criticality check is elsewhere. Change-Id: I889f6ebf4ca4b34b1d9ff15f45e05878132826a1 Reviewed-on: https://boringssl-review.googlesource.com/28549 Commit-Queue: David Benjamin <firstname.lastname@example.org> Reviewed-by: Adam Langley <email@example.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.
There are other files in this directory which might be helpful: