|author||Adam Langley <email@example.com>||Fri Sep 11 18:16:05 2020 +0000|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Fri Sep 11 18:37:33 2020 +0000|
Revert "Check AlgorithmIdentifier parameters for RSA and ECDSA signatures." This reverts commit 9dd9d4fc242f31584f5a42e41e63d132c790421f. BUG=b/167375496,342 Original change's description: > Check AlgorithmIdentifier parameters for RSA and ECDSA signatures. > > This aligns with the Chromium certificate verifier, which allows NULL or > empty for RSA and requires empty for ECDSA. > > Bug: 342 > Change-Id: I34acf68f63b4d133dd47b73144b2f27224c499ee > Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/41804 > Reviewed-by: Adam Langley <firstname.lastname@example.org> > Commit-Queue: David Benjamin <email@example.com> TBRfirstname.lastname@example.org,email@example.com # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: If8f136a09fea68e64c9f4f9ffae88b6209ede124 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/42804 Commit-Queue: Adam Langley <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: