| commit | 91e0b11eba517d83b910b20fe3740eeb39ecb37e | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Sep 13 01:23:52 2022 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 13 18:04:21 2022 +0000 |
| tree | 07e3dec12d36e391c8d7bf5d5b3816954c507f0d | |
| parent | 1b2b7b2e70ce5ff50df917ee7745403d824155c5 [diff] |
Use the new macOS sysctl names when available At the time, there was no documentation (or I just couldn't find it) on the correct sysctl names to query CPU features on Apple aarch64 platforms, so it was unclear what the relationship was between "hw.optional.arm.FEAT_SHA512" and "hw.optional.armv8_2_sha512". There is documentation now: https://developer.apple.com/documentation/kernel/1387446-sysctlbyname/determining_instruction_set_characteristics However, the documented names weren't available in macOS 11, and some Arm Macs did ship with macOS 11. So query both names for macOS 11 compat and in case some future version of macOS removes the old names. Change-Id: I671d47576721b4c172feeb2e3f138c6bc55e39d6 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54445 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@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:
There are other files in this directory which might be helpful: