Check extensions on the trust anchor too This gets most of trust anchor extension enforcement. I believe the only thing remaining is how much of policy validation should look at the trust anchor. (I'll need to remind myself of the quirks of RFC 5937 and the place libpki opted to diverge.) Update-Note: Critical extensions, EKU, and path length constraints are now checked on the trust anchor, the same as if they were on an intermediate. This aligns with OpenSSL, except that OpenSSL has some extra quirks around the EKU check, that we for now do not replicate. Bug: 525688038 Change-Id: I0a3cf64a81e44c3637e8050cce97aefa4235c320 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/104309 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: