Remove odd special case around policy validation This once made sense when policy validation was a DoS concern. But after https://boringssl-review.googlesource.com/c/boringssl/+/56036, this doesn't make sense. It also is not much of a DoS protection. Either way, we run policy validation after all other checks have passed, so typically an invalid chain won't get this far. This check only matters if the caller suppresses enough errors with the verify callback to proceed with an invalid chain. Change-Id: I5845e1dc6d6ef6f80398f8c1e37cf9346658d777 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/103867 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Lily Chen <chlily@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: