acvptool: seed key format for ML-DSA sigGen and ML-KEM decap ACVP-Server v1.1.0.43 adds the FIPS204-tr1 and FIPS203-tr1 testing revisions. These add a keyFormats registration property that lets an implementation under test receive the ML-DSA sigGen private key or the ML-KEM decapsulation key as a seed instead of in expanded form. Test groups with keyFormat "seed" are dispatched to new module wrapper commands, ML-DSA-XX/sigGen/seed and ML-KEM-XX/decap/seed. The seed for ML-KEM is d followed by z, as in keyGen. Groups with expanded keys use the existing commands unchanged. The BoringSSL module wrapper implements the new commands with the existing from-seed functions. The new test bz2 vectors/expected were fetched from the NIST demo server and the answers validated there successfully before trimming. Change-Id: I0826c01074f1d08a15eae14b3935964f82e9a749 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/100087 SLSA-Policy-Verified: SLSA Policy Verification Service <devtools-gerritcodereview-exitgate@google.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com> Reviewed-by: 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:
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: