util/fipstools: allow rsakpg2-[basic|crt] for KTS-IFC Previously the fipstools kts subprocess code rejected test groups that corresponded to capabilities advertising keyGenerationMethods using anything other than rsakpg1-basic (fixed pub exp, basic format) or rsakpg1-crt (fixed pub exp, crt format). This commit extends the check to also allow rsapkg2-basic (random pub exp, basic format) and rsapkg2-crt (random pub exp, crt format). The exponent (fixed or random) is already passed through to the module wrapper so no further code changes are required in the acvptool to support testing modules using random exponents for KTS-IFC. Change-Id: I79e941a5ac6ddbd7068cb1067b9d8b449b70e0a4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/92527 Reviewed-by: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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: