pki: Add trusted subtrees to CertificateTrust Makes the trusted_subtrees_ field of MTCAnchor store it as a std::shared_ptr, which is then copied into the CertificateTrust representing the MTCAnchor. Along the way, remove constexpr from CertificateTrust, and make a new type, TrustedSubtreeSet, holding a std::vector<LogTrustedSubtrees> to handle validation and lookup of trusted subtrees. After this change, logic for handling trusted subtrees no longer lives in MTCAnchor. Changes the TrustAnchor::CertTrust() getter to return a reference since CertificateTrust copies are no longer free. This is a step towards making trust anchors uniformly representable as a (ParsedCertificate, CertificateTrust) pair, pivoting away from the earlier plan of migrating the representation of all trust anchors to the TrustAnchor type. Bug: 575507260 Change-Id: I45aea0a3f0a1f1e75093d8b8408ec3086a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/104988 Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Matt Mueller <mattm@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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: