ACVP: test non-canonical ML-KEM keys. The existing ML-KEM ACVP fixture only covers valid encapsulation keys. Older NIST-generated invalid keys had unintended lengths, so they did not exercise rejection of non-canonical polynomial coefficients. Add a focused NIST demo fixture for ML-KEM-768 and ML-KEM-1024. Each parameter set includes a valid key and a correctly sized invalid key whose first coefficient is 3330, outside the canonical range 0 through 3328. The full response was accepted by the NIST demo server before trimming. Keep these cases separate from ML-KEM.bz2 so the regression stays explicit without replacing unrelated ML-KEM coverage. Change-Id: Ic31b4a843b53d8749a3cf3d6a6a56f777152a8de Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/101367 Reviewed-by: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> SLSA-Policy-Verified: SLSA Policy Verification Service <devtools-gerritcodereview-exitgate@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: