| commit | d18c9f2395f9140d1a8a439fe1cc7ebb9728c060 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Oct 10 16:13:27 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 21 12:06:50 2025 -0700 |
| tree | 3749fb83cc95cdb56b2832d63702bac769f7899b | |
| parent | 4f36cc932045abfb52997dc024a6d29d2dd5a635 [diff] |
Remove some easy OPENSSL_EXPORTs In principle, nothing in private headers should be OPENSSL_EXPORT. But we've been a bit sloppy with unit tests (in hindsight, that maybe would have been better done by static linking), and also sloppy in some FIPS test binaries, so quite a lot of the BCM functions are OPENSSL_EXPORT. These are the easy ones to undo. I've left the postquantum stuff alone for now. Change-Id: I13d954338a88c3534ffe27f1da7d0181847662bd Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82987 Reviewed-by: Lily Chen <chlily@google.com> Commit-Queue: Lily Chen <chlily@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: