Revert "Make all non-asm-included BoringSSL headers at least include <openssl/base.h>." This reverts commit 86101b72bbb93913a00a79ac614b138633c1f4a4. Reason for revert: downstream build breakage Failure Link: test/OCL:979213230:BASE:979210442:1789060697838:55730749 Original change's description: > Make all non-asm-included BoringSSL headers at least include <openssl/base.h>. > > This guarantees that any successful header include provides at least the > basic macros like `OPENSSL_IS_BORINGSSL`. > > Change-Id: If9cbce85eac9aebcf6890524d3f05c7c6a6a6964 > Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/99787 > Auto-Submit: Rudolf Polzer <rpolzer@google.com> > Reviewed-by: Xiangfei Ding <xfding@google.com> > Commit-Queue: Xiangfei Ding <xfding@google.com> # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: I598fa8f39ca8746e3c8526c1f8f9431dd16f3e85 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/102687 Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> Auto-Submit: 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: