| commit | 3494965215d3a4ac44c30c2929194dd66089781d | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@chromium.org> | Sun Feb 16 10:19:56 2025 +0000 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 03 16:07:04 2025 -0800 |
| tree | 5ff581403f0836da8469c55e857c925827f4e409 | |
| parent | 5e73d0302c50cc38324686f937a75233d13ae4f0 [diff] |
Add ML-DSA self tests. Change-Id: I640b1f57de2544d9329cba83352d0d51debc092c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/76388 Commit-Queue: 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: