| commit | f7543e6dbbcf555557fb8d53ef1ff5b9fe393a1d | [log] [tgz] |
|---|---|---|
| author | Rudolf Polzer <rpolzer@google.com> | Wed Jan 07 08:26:43 2026 -0800 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 19 02:29:43 2026 -0800 |
| tree | 47c8dae45a6ad083d691176a3bb1dfd52efb9c4c | |
| parent | 4003f6d045b9b330cee4b4a6fe65e7fc79d99fa0 [diff] |
Namespace crypto/internal.h's internal symbols. Down from 65 to 3 unintended exported symbols. The remaining 3 are weak symbols to override the malloc implementation and might be acceptable (and if not, they probably will be prefixed like public symbols instead): extern "C" function OPENSSL_memory_alloc; // crypto/mem.cc:103 (4077-4093) size extern "C" function OPENSSL_memory_free; // crypto/mem.cc:104 (4139-4155) ptr extern "C" function OPENSSL_memory_get_size; // crypto/mem.cc:105 (4196-4212) ptr This has been confirmed acceptable, and is likely required by existing code bases linking to BoringSSL. Bug: 42220000 Change-Id: I5c7be4e12ef0aa09691e0bc938bfc6c76a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/86669 Reviewed-by: Xiangfei Ding <xfding@google.com> Commit-Queue: Rudolf Polzer <rpolzer@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: