| commit | b67530a5766715c9fd0efc36c9a119433604c6d4 | [log] [tgz] |
|---|---|---|
| author | Daniel McCarney <daniel@binaryparadox.net> | Fri Jan 30 13:36:41 2026 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 30 17:07:26 2026 -0800 |
| tree | 6cebae79fd063db3d342e1c12eed163819973032 | |
| parent | 8a62e3c5e84e252ff649794abf8a541a8f30877e [diff] |
util/fipstools: add ACVP KTS-IFC crt support Previously the FIPS acvptool KTS subprocess support required keyGenerationMethods=rsakpg1-basic, citing a requirement for fixed public exponents. This commit extends support to include rsakpg1-crt, another fixed public exponent form that provides the keypair in Chinese Remainder Theorem (CRT) format. This requires the acvptool to provide the modulewrapper different arguments for the responder role than it would otherwise (sending dmp1, dmq1, iqmp and no d), so the new command "KTS-IFC/$DIGEST/responder/crt" is used to differentiate from "KTS-IFC/$DIGEST/responder", the pre-existing command that assumes basic keyFormat. See https://pages.nist.gov/ACVP/draft-hammett-acvp-kas-ifc.html for more information Change-Id: Ia02d1fe58f03fbe92f3d18752f33260f78518111 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88387 Reviewed-by: Adam Langley <agl@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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: