| commit | 2278a49bfef420ba40728fb63776f1ac2a0d4fde | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Dec 03 16:35:16 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 03 22:06:39 2024 +0000 |
| tree | 91a5acd53240f9728d1d246d57581a0229deae33 | |
| parent | 2635bedc5d12407e4e78f2250d9c8c534954e045 [diff] |
Remove Dilithium in favor of ML-DSA For some reason, marking the symbols as deprecated resulted in some warnings in crypto/dilithium/dilithium.cc that I cannot reproduce. Perhaps behavior differences across GCC versions? See https://buildkite.com/bazel/bcr-presubmit/builds/9152#01938e2a-497a-4100-9774-f7e4a8ed692a Regardless, this code was due to be removed anyway, so just remove it. Update-Note: The pre-standard Dilithium construction has been removed. Use ML-DSA instead. Change-Id: I72e54e838772abd8230cd435a4015104cd0e0251 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73907 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> Auto-Submit: 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: