Namespace crypto/x509's internal symbols. Note that this means structs that were only internally declared as ASN1 items no longer export the ASN1 item functions. In case any external code used DECLARE_ASN1_ITEM on those, it might no longer work. None such instances exist in google3 and Debian: https://codesearch.debian.net/search?q=DECLARE_ASN1_ITEM%28X509&literal=1&perpkg=1 lists only one match outside whole copies of OpenSSL or BoringSSL, and that one's X509_ALGOR which already is a public ASN1 item and not changed by this commit. Down from 303 to 65 unintended exported symbols. Bug: 42220000 Change-Id: I4049c022da811c4885ef829986d011c3d1eb5796 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/86207 Reviewed-by: David Benjamin <davidben@google.com> Reviewed-by: Xiangfei Ding <xfding@google.com> Commit-Queue: Rudolf Polzer <rpolzer@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: