| commit | 4bc7c0f06085051e5625b519b32060a77fb15b54 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jan 10 16:27:34 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 13 11:46:37 2025 -0800 |
| tree | fad70c28df9194aa91f16664592b34f0a6d4a4c9 | |
| parent | 628b161fc2836b5d5605f073703819b3829d32c6 [diff] |
Initialize iqmp during keygen directly freeze_private_key mostly existed to fill in cached values, but it also would compute iqmp for keygen. Instead, just compute iqmp in keygen. This does mean we have two places where we might construct mont_p, but this should make moving the initialization process around a bit cleaner. This does mean we'll no longer silently fill in a missing iqmp, but I don't believe this is an externally-visible behavior change. RSA_set0_crt_params won't let you set iqmp without also setting dmp1 and dmq1. Bug: 42290186 Change-Id: Ib625d41e665efaf3b6a068fe9b6eb40b9da8ee29 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/75150 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@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: