| commit | 9bb8f779a7287dd11d02e25fe1a91e1d902d917e | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Feb 13 13:46:47 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 18 08:32:02 2025 -0800 |
| tree | 93a3584308a64ac10633f52b17d5073ca3839211 | |
| parent | 1a42cb8b270248be545c926eee58bf3e89f7f69a [diff] |
Remove now unnecessary <openssl/arm_arch.h> includes from assembly This header used to supply CPU capability constants and things like __ARM_MAX_ARCH__. The latter is now part of asm_base.h, automatically included by everything, and assembly files no longer do capability checks. The immediate motivation was that there were a few misspelled includes that used "openssl/arm_arch.h" instead of <openssl/arm_arch.h> (see https://boringssl-review.googlesource.com/c/boringssl/+/76247), but given we can just remove them anyway, may as well clear this out. This now also means we don't pollute another prefix in the global namespace (though external callers shouldn't have been using this header anyway). I've kept the header around, but a no-op, because some bindings libraries have explicitly listed the header and it's probably not worth the trouble to clear those out. Bug: 42290548 Change-Id: I24f36cd48b0e3b6498ecbdc70fecc36961a8b9fe Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/76248 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: Bob Beck <bbe@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: