| commit | 61780c6123af0cc8b85e20ea200f17f1604394b1 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Jun 23 13:58:03 2025 -0400 |
| committer | David Benjamin <davidben@google.com> | Mon Jun 23 12:38:48 2025 -0700 |
| tree | f80b6a899806bd526bcbff9591768d91a7a8c260 | |
| parent | f51d8b099832f805022a6ff2e9466dbcacdfb0ab [diff] |
Don't suppress CMAKE_(C,CXX)_FLAGS in MSVC builds All this time, since the very start of the project, our MSVC builds have ignored the caller-supplied CMAKE_(C,CXX)_FLAGS on accident. This means, all this time, we have never been using our OPENSSL_SMALL builds on CI because those happened to set -DOPENSSL_SMALL in CMAKE_(C,CXX)_FLAGS rather than the CMake toggle. As a result, crbug.com/427018041 did not get noticed on CI. Whoops! Update-Note: MSVC builds that pass CMAKE_(C,CXX)_FLAGS will start to actually honor those flags. That it didn't work before was a long, long-standing bug. Bug: 427018041 Change-Id: I5be9d407b0aa37e2061257e4711f06e9711cfcfa Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79847 Reviewed-by: 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: