| commit | 453207b73e9997cd49f79fee98843255638e74a4 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@chromium.org> | Tue Oct 22 15:42:30 2024 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 23 00:24:31 2024 +0000 |
| tree | b7eaeeb4e8f40afc70ddd1d507d6a765e93a7464 | |
| parent | ce572d6e9bde836016b200169abf81e71b2a55bf [diff] |
Have modulewrapper print more of its build environment. It's useful for auditing purposes if modulewrapper can print information about the FIPS module within it. Also, we have a function, `CRYPTO_has_asm`, which reports whether assembly code is enabled or not. But that function wasn't implemented within the FIPS module and thus it reported the condition of libcrypto instead. This change moves it into the FIPS module so that it reports the condition there, which is what we care about. Change-Id: I66ac8936c6d8dd7b5260ec7a68405d58a63990fb Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72327 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> Auto-Submit: 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: