|author||David Benjamin <firstname.lastname@example.org>||Sat Jun 20 02:56:15 2020 -0400|
|committer||David Benjamin <email@example.com>||Fri Nov 06 22:01:01 2020 +0000|
Unwind ASN1_TFLG_NDEF. Sadly we need to keep ASN1_put_eoc. Ruby uses it. OpenSSL's PKCS#7 implementation generated an "ndef" variant of the encoding functions, to request indefinite-length encoding. Remove the support code for this. Update-Note: Types that use one of the NDEF macros in asn1t.h will fail to compile. This CL should not affect certificate parsing. Change-Id: I6e03f6927ea4b7a6acd73ac58bf49512b39baab8 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/43889 Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: