| commit | 9a8c72d91959f68fe86291b5d07557a7f1cee906 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Feb 03 17:12:20 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 04 10:38:53 2025 -0800 |
| tree | 208011deb8164f47ea0c68e7f0066e63d3fd3673 | |
| parent | ea42fe28775844ec8fe0444fc421398be42d51fe [diff] |
Restore the __SHA__ compile-time check for Intel SHA Extensions It's been about a year since the CrOS toolchain was fixed, and QEMU 8.2 has been around for a while. Let's see if it works. Update-Note: If SHA starts crashing on illegal instruction, check if you are building in a configuration that assumes Intel SHA extensions (e.g. -march=goldmont) and then running on a machine that lacks them. (If using QEMU, update to QEMU 8.2 or later to be able to correctly emulate a processor with SHA extensions.) If so, let us know, though if you can simply fix your build, that's simplest. Bug: 320482539 Change-Id: Ie4584cde452a1ff9416fbac89369813a6991ff8a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/75869 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: David Benjamin <davidben@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: