commit | 2cc2aa9f60f232e19ff042d152b363c64d348576 | [log] [tgz] |
---|---|---|
author | Adam Langley <agl@chromium.org> | Tue Jul 26 07:12:34 2022 +0000 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 26 17:08:35 2022 +0000 |
tree | 415dec88f1c6a81babf8735c0f887747985a2920 | |
parent | b95c7e53d7d4376dbba18c3e3bbba99d66e3fbff [diff] |
Don't try to specify SHA-256 for Aarch64 FIPS. 27ffcc6e19bba switched the integrity check to using SHA-256, but the Aarch64 FIPS build was still passing -sha256 to inject_hash.go. Change-Id: I641de17d62205c7f127cd2a910d4e98778d492e7 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/53605 Reviewed-by: David Benjamin <davidben@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:
There are other files in this directory which might be helpful: