| commit | 305bcfce00b189f2297f53365b0454f96009927d | [log] [tgz] |
|---|---|---|
| author | Daniel McCarney <daniel@binaryparadox.net> | Mon Feb 02 14:24:17 2026 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 06 06:25:00 2026 -0800 |
| tree | f1198226b673b4356974f8dd4f9a78a0b2b43861 | |
| parent | 4db204316f358eb223b4858e35abe2b4c262112a [diff] |
util/fipstools: saltLen arg for ACVP RSA/sigGen/pss cmd The ACVP capabilities for RSA sigGen allows specifying a PSS sigType saltLen between 0 and the digest size (in bytes) of the associated hashAlg. This commit updates acvptool to provide the saltLen value as an argument to the RSA/sigGen/$DIGEST/pss command for the module wrapper to process. Change-Id: I552e65ad6ebed610a8545651af3c63fa3b46fef9 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88467 Reviewed-by: Xiangfei Ding <xfding@google.com> Commit-Queue: Xiangfei Ding <xfding@google.com> Reviewed-by: Rudolf Polzer <rpolzer@google.com> Reviewed-by: 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: