| commit | 830e786772558fa9b80aa7e7118aaa5b2a042344 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@chromium.org> | Thu Nov 21 16:32:38 2024 -0800 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 11 16:07:37 2024 -0800 |
| tree | adbf8f352f254f4c0006d54cab28e44e45db8692 | |
| parent | 48d150f5940a3fd1a41cd0ce067887efa97fb2be [diff] |
ML-DSA ACVP Wire up ACVP tests for ML-DSA which is newly in the FIPS module. Change-Id: Iea2edd3bc0a29c53419bd6df675c139337fbce2a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73367 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: 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: