util/fipstools: ACVP RSA keyFormat=crt keyGen Support ACVP testing of RSA capabilities where the keyGen keyFormat is crt. This requires the modulewrapper return more results than it would otherwise, so the new command "RSA/keyGen/crt" is used to differentiate from "RSA/keyGen", the pre-existing command that assumes standard keyFormat. See https://pages.nist.gov/ACVP/draft-celi-acvp-rsa.html#section-7.3 for more information. Change-Id: I97cfd81e5849d38a388062d30c8c695ea9246669 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/87747 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: 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: