| commit | b8c97f5b4bc5d4758612a0430e5c2792d0f9ca7f | [log] [tgz] |
|---|---|---|
| author | Daniel McCarney <daniel@binaryparadox.net> | Thu Oct 24 13:25:55 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Oct 26 00:49:21 2024 +0000 |
| tree | 83550b2b65d480a9a5f5a32de2fca3d89a413a5d | |
| parent | 971951f15d76cfef611c59b7694236fd14b279e6 [diff] |
utils/fipstools: add SHAKE-128/256 ACVP support This commit extends the acvptool subprocess package to support the SHAKE-128 and SHAKE-256 test vectors and expected responses defined by draft-celi-acvp-sha3: https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.html The AFT test type is a close match to the existing SHA2/SHA3 AFT test type, but VOT (variable output test) and MCT both differ enough that it feels most clear to treat each as separate commands with their own subprocess primitive. The ACVP.md documentation of available commands is also updated to describe the pre-existing SHA3 commands. Change-Id: Ib5e468331f0c37e8298ff8e6a2bfa9665d954e83 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72467 Reviewed-by: Adam Langley <agl@google.com> Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: 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: