| commit | 296ef284e51a687920a1975a1a34fd2ffce0a646 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Aug 28 18:08:18 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 28 23:46:28 2024 +0000 |
| tree | b44c86233aa4681eda9477ea0a86c388ea71ec1e | |
| parent | 0b8ef03132edfeeeeb7c9b73124146ffc5c85ec5 [diff] |
Disable parse_headers feature Bazel has a parse_headers feature which expects headers to be independently buildable. While a nice way to partially enforce IWYU, it's broken. See https://github.com/bazelbuild/bazel/issues/23460. Until the Bazel issue is fixed, we'll need to turn that off. In particular, after https://github.com/bazelbuild/bazel/pull/22369, parse_headers is no longer silently inactive. This does not remove the need to do something about the fips_fragment filenames. Those come from the layering_check feature, rather than the parse_headers feature. We also have a number of headers that don't actually work standalone and, by the style guide, probably should be named .inc: https://google.github.io/styleguide/cppguide.html#Self_contained_Headers But since the feature does not work anyway, just turn it off for now. Bug: 362664827 Change-Id: I9646d722a59f92be81848cf5a586738cc5f3dac4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70687 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: Bob Beck <bbe@google.com> Auto-Submit: 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: