commit | 6a2ccdcc2ed1d37a43a2183658d2ae61fd5ce208 | [log] [tgz] |
---|---|---|
author | Adam Langley <agl@chromium.org> | Wed Sep 11 15:59:46 2024 -0700 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 13 15:55:11 2024 +0000 |
tree | 43b2a00664cf9c80acb7b83eb6a66b6213e718fe | |
parent | e724ef02089bf2bb494203231fc5cb62acc2fad6 [diff] |
Don't define `OPENSSL_cpuid_setup` in NO_ASM builds. The prototype isn't included by the preprocessor if OPENSSL_NO_ASM is defined thus defining the function is an error. Change-Id: I7176bb2c406f5597ae4033274141f69342a2b226 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71167 Reviewed-by: David Benjamin <davidben@google.com> Auto-Submit: 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: