commit | 4509dc7a88b1f11d44ed3689df470c773dd7977e | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Wed Dec 18 17:39:27 2024 -0500 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 18 14:58:20 2024 -0800 |
tree | 0f2d6421f645e250a3c29e057e87d6b3ff29eaec | |
parent | 3dc7237a875d6d004a9a20546b26e1e42c58bba6 [diff] |
Also run Kyber through constant-time validation This is the same as what we did for ML-KEM earlier. The Kyber code will be removed in not too long, but since we haven't quite removed it yet, let's run it through the same thing. Change-Id: Ie0833d88fd49c4b475e1512d3f3b8f44c9e1fc66 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/74567 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@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: