Reapply "Simplify the symbol prefixing macros." This reverts commit 9b4d8692731864f624593083326c407a8fe25ba4. The headers are now always included, but check for BORINGSSL_PREFIX themselves; also, the macros use less case distinctions now. This reduces the RAM usage of the compiler, but also is generally nicer in the sense that it now properly autodetects the need to prepend an underscore rather than relying on Apple vs non-Apple. It also is part of a potential workaround to use the #pragma redefine_extname together with precompiled headers. Update-Note: <openssl/prefix_symbols.h> is now always included. Downstream build systems may need changes to add this file to the build dependencies. Similarly, nasm files now always include "boringssl_prefix_symbols_internal_*.inc" from gen/, and thus build systems may need to add the directory to the include path. Now the Chromium build should have been fixed. Bug: 42220000 Change-Id: I9bf318e4d80a21aaa4f053bb17249bd96a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/90408 Reviewed-by: Xiangfei Ding <xfding@google.com> Commit-Queue: Xiangfei Ding <xfding@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: