| commit | 673e61fc215b178a90c0e67858bbf162c8158993 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Feb 28 17:25:36 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 28 15:12:34 2025 -0800 |
| tree | cd2d6dd22e9aa5eb49c442bb384ae53c7b02dca0 | |
| parent | ad62e9cab15536b1db61a7cb7b316f6fb3e9e563 [diff] |
delocate: remove the need to demangle local variables We need to demangle because the backing storage for a delocated BSS symbol is declared static. The compiler seems to be always give it a C++-mangled name. But we relied on those names to infer the names of the bss_get functions that the rest of the code wanted. Instead, if we make the backing storage non-static, we get the name we want. Ideally we would avoid having to extract those names (see https://boringssl-review.googlesource.com/c/boringssl/+/70849), but faking the linker script behavior in delocate seemed tricky, so I opted to do this and then we can finish up the linker script version later. While I'm here, prefix the underlying names with 'bcm_' so we're not squatting as much of the namespace. Change-Id: I1ce9a189e620c872511dbce09d23e655f1593d34 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/76847 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: