| commit | a0a089e60c13c1fc85b3362c8196ea48dd619ec7 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jan 09 13:04:45 2026 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 09 10:21:08 2026 -0800 |
| tree | 6d77f4e944c8ebd7bf690c814a9c6b5a1f520799 | |
| parent | ff190b7890e9b7f96a731229a19265134ab18d3a [diff] |
Fix build with -Wheader-hygiene The `using namespace bssl` pattern causes BCM fragments to flag -Wheader-hygiene on Clang. For now, suppress it in the BCM fragments and enable it in our build so we catch future issues. This is slightly precarious because those namespace declarations *do* leak across the constituent files. But for now, let's keep running with this convention and see how it goes. Perhaps one day we'll stop needing this jumbo build (crbug.com/362530616), or perhaps we'll settle on a different solution for the awkward C/C++ linkage mix we're stuck in. It seems -Wheader-hygiene has been around since LLVM 3.0, so we shouldn't need to gate it on a version check. Bug: 42220000 Change-Id: Ie82fc19e81dd467b4ad4d4837b42bcc350b0cf0c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/86827 Commit-Queue: Lily Chen <chlily@google.com> Reviewed-by: Lily Chen <chlily@google.com> Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: 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: