| commit | ec8ba76739f3270a82ae7c18fb88baea3fe25217 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Dec 17 15:41:36 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Dec 22 09:35:49 2025 -0800 |
| tree | da47b281a95b3cf7a56604e38447dc47db6bcbed | |
| parent | b74ac2be734c59f59a6f0a7930487bb7b0e4bc26 [diff] |
Compute the FIPS module hash after evaluating relocations Our build currently requires the BCM text segment to have *no* relocations, but that's a little strong. It is sufficient for it to have only link-independent relocations. I.e. relocations that always give the same result no matter what it is linked against. In a sufficiently smart toolchain, these would be the same, but sometimes we get these. On AArch64, ADRP always emits a relocation in Clang's assembler, even when the page offsets are known due to alignment requirements. The linker script idea in crbug.com/362530616 also emits a ton of these because `ld -r` does not know how to partially evaluate relocations. As part of this, build bcm_hashunset as a CMake object library instead of a CMake static library. If it's a static library, CMake gets very upset about the shared library having no sources, and keeps trying to drop the static library as unused. Update-Note: See also cl/846024477 Bug: 362530616, 469788763 Change-Id: I2f1999679b1987664da4350d86ac149e52d44303 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/85928 Reviewed-by: Adam Langley <agl@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: