| commit | 514abb73bb80130000b46cf589190c967c6647cd | [log] [tgz] |
|---|---|---|
| author | Xiangfei Ding <xfding@google.com> | Thu Feb 05 04:51:25 2026 -0800 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Feb 05 04:55:47 2026 -0800 |
| tree | 5617ba84ad61603d5d703add41166dd42fe86442 | |
| parent | eddaea9a812e09216ea8c07535f96bfc0306ab44 [diff] |
Revert "Add support for ML-DSA `ctx` parameter. Add corresponding tests" This reverts commit e0455c792569a6826d201a6ed514d1e0a24e077e. Reason for revert: MLDSA and MLKEM EVP support is still under construction. Original change's description: > Add support for ML-DSA `ctx` parameter. Add corresponding tests > including a fix of a segfault in setting up context for the > VerifyMessage scenario. > > Change-Id: Ie1e24b8e5e38c8856e7b67ff3d97fabc00620429 > Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88607 > Reviewed-by: Xiangfei Ding <xfding@google.com> > Commit-Queue: Xiangfei Ding <xfding@google.com> TBR=agl@google.com,davidben@google.com,boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com,xfding@google.com,lizatretyakova@google.com No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: Icf513490aae4c563a1bf704c492c1d3a3568fcee Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88727 Reviewed-by: Rudolf Polzer <rpolzer@google.com> Commit-Queue: Xiangfei Ding <xfding@google.com> Reviewed-by: Xiangfei Ding <xfding@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: