Revert "Namespace crypto/trust_token's internal symbols." This reverts commit bb9a6cc1237421527806ff33d85961a59e68337e. Reason for revert: looks like a lot of code depends on STACK_OF(T) expanding to stack_st_T. Original change's description: > Namespace crypto/trust_token's internal symbols. > > Required adding namespace support to `BORINGSSL_DEFINE_STACK_TRAITS`. > > Down from to 1019 to 949 exported symbols. > > Bug: 42220000 > Change-Id: I89bd01bd030c854320cf3e16984d0e2e22640591 > Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/86050 > Auto-Submit: Rudolf Polzer <rpolzer@google.com> > Reviewed-by: Xiangfei Ding <xfding@google.com> > Reviewed-by: David Benjamin <davidben@google.com> > Commit-Queue: David Benjamin <davidben@google.com> TBR=davidben@google.com,boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com,rpolzer@google.com,xfding@google.com No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 42220000 Change-Id: I3bad910aa76740d1bb11e0fe1baa77e9cef9a82a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/86587 Reviewed-by: Lily Chen <chlily@google.com> Commit-Queue: Lily Chen <chlily@google.com> Auto-Submit: 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: