| commit | fc03aae5d669b1735ac26cad31823cce49063803 | [log] [tgz] |
|---|---|---|
| author | Daniel McCarney <daniel@binaryparadox.net> | Wed Oct 09 15:39:46 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 09 20:31:33 2024 +0000 |
| tree | 8b53f708007d69e1884cda300fba0911ffc67022 | |
| parent | d0a175601b9e180ce58cb1e33649057f5c484146 [diff] |
util/fipstools: SHA2-512-224 ACVP primitives Previously `SHA2-512/256` and `HMAC-SHA2-512/256` were supported, but not `SHA2-512/224` and `HMAC-SHA2-512/224`. This commit adds both as known primitives since they are listed as supported by the NIST ACVTS[0][1]. Without this change a module wrapper advertising capabilities for either algorithm produces a "wrapper config advertises support for unknown algorithm" error message. [0]: https://github.com/usnistgov/ACVP?tab=readme-ov-file#secure-hash [1]: https://github.com/usnistgov/ACVP?tab=readme-ov-file#message-authentication Change-Id: Ica3c79cdf3b04712533355b9fdbed83534905800 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71887 Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Adam Langley <agl@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:
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: