Revert "crypto/x509: Verify standalone Merkle Tree Certs (MTCs)" This reverts commit f89068d3030374395c4b070838d1f4d9bbef5465. Reason for revert: build failure crbug.com/549361069 Failure Link: https://ci.chromium.org/ui/p/chrome/builders/try/linux-chrome-dbg-cog-cache-warmer/79105/overview Original change's description: > crypto/x509: Verify standalone Merkle Tree Certs (MTCs) > > This implements verification of "standalone" Merkle Tree Certs (see > draft-ietf-plants-merkle-tree-certs-05, section 6.3) as part of the > X509_STORE_CTX API, if the flag X509_V_FLAG_USE_MTC_DRAFT_PLANTS_05 > is specified. > > Bug: 503746594 > Change-Id: Ie5abd17eb34c37139d3be1261e1914976a6a6964 > Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/100707 > Reviewed-by: David Benjamin <davidben@google.com> > Commit-Queue: Lily Chen <chlily@google.com> > Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> TBR=davidben@google.com,boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com,chlily@google.com No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 503746594, 549361069 Change-Id: If43293ba7c2199a463a98dcf848fcc60bdd1e9bb Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/101307 Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Auto-Submit: Lily Chen <chlily@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@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: