Don't detect pre-C++11 in <openssl/base.h> When we first added bssl::UniquePtr, we added a __cplusplus version check to tolerate C++98 and C++03 consumers of our public headers, and only giving them the C symbols. It is now 2025. Since then, we've added <openssl/span.h> and written C++17-requiring code in it, so C++11 and C++14 consumers of public headers already broke. No longer try to bifurcate our consumer and implementation C++ versions. Update-Note: C++ projects including BoringSSL headers now must be C++17 or later, matching the requirement for building BoringSSL. C projects are unaffected. C++ projects that were previously building at C++98 or C++03 will need to update to a language version from sometime in the last couple decades. Change-Id: I9e6ae1807398e5363ff71e0d2a83bfaa3f8bcbfc Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/84947 Commit-Queue: Rudolf Polzer <rpolzer@google.com> Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: 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: