| commit | ed322d7e9684066142149440a375455f62ee067a | [log] [tgz] |
|---|---|---|
| author | Daniel McCarney <daniel@binaryparadox.net> | Fri Oct 18 18:45:42 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 22 17:06:49 2024 +0000 |
| tree | 7523719fff77389e1601609e213050d9b39c6606 | |
| parent | fb5b271624ec0344d4ec800b4f89dc84cada741a [diff] |
util/fipstools: add EDDSA ACVP support This commit extends the acvptool subprocess package to support the EDDSA test vectors and expected responses defined by draft-celi-acvp-eddsa: https://pages.nist.gov/ACVP/draft-celi-acvp-eddsa.html There was a pre-existing registration for the "EDDSA" command, but it was using the ecdsa.go subprocess code that isn't a match to the EDDSA specification. No EDDSA capabilities were being claimed in the modulewrapper.cc or testmodulewrapper.go JSON so I suspect this was perhaps the start of unfinished support (?). There are a few quirks for EDDSA compared to ECDSA beyond the differences in vectors/expected results. Notably there is the option to advertise the prehashed capability to exercise Ed25519ph. To facilitate the testmodulewrapper being able to implement EDDSA keyVer there's a new dependency added on Filippo's edwards25519 package. The go stdlib equivalent is not exported for external use. Change-Id: Id0571470202a2761125cc9af3c5f0593b0b94ccc Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72207 Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@google.com> Reviewed-by: Adam Langley <agl@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: