Gate VAES codepaths on is_hwaes to fix a theoretical concern This is a theoretical concern because no x86 CPU has VAES without AES-NI. However, since we have the testing-only environment variable, it is in theory possible for someone to set the wrong thing. This is easy enough to add, so we may as well, but we do not, in general, consider unreasonable CPUIDs to be in scope. (There are other environment variables like LD_PRELOAD that do even more uncontrolled things! And reruning tests across every possible fake CPUID is unreasonable. At least real CPUIDs are bounded.) I've filed crbug.com/552976703 to consider whether we want to keep this thing. Fixed: 552666770 Change-Id: Ie5909ffb953f97286fba7b61ab09a5a436a0cef4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/101787 Reviewed-by: Adam Langley <agl@google.com> Auto-Submit: David Benjamin <davidben@google.com> Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: Adam Langley <agl@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: