| commit | 683262795801abab5d0d5b2dd533d82dcfd64248 | [log] [tgz] |
|---|---|---|
| author | Daniel McCarney <daniel@binaryparadox.net> | Wed Dec 11 17:01:52 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 11 15:22:59 2024 -0800 |
| tree | 6c401b730b43c03c3b2718ddb768860251443ed8 | |
| parent | ea92d98040761248d50d05654242d9c2dfbadcba [diff] |
utils/fipstools: add DetECDSA ACVP support Very little needs to change in acvptool in order to support the deterministic ACVP algorithm spec from the NIST spec: https://pages.nist.gov/ACVP/draft-fussell-acvp-ecdsa.html Only the sigGen test mode is specified for this algorithm, and without any support for the componentTest property, so we make sure to check these are sane when processing DetECDSA algorithm vectors. A module wrapper only needs to know it's DetECDSA and can otherwise treat the operation the same as ECDSA/sigGen. Change-Id: Iecd3dc79d31f448272accd63ef24c882c3fc3b55 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/74189 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Bob Beck <bbe@google.com> Reviewed-by: Adam Langley <agl@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: