| commit | 87c00d522b6c7be2f11eb967705d73a7271a0a64 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Aug 11 18:56:16 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 14 21:10:48 2023 +0000 |
| tree | e1d969b89d8512d55f2c4e0074453258e64f2a6a | |
| parent | c3b236d325bbdcbb4621815704c7e7e927923042 [diff] |
Align DH keygen with NIST's formulation when q is available Section 5.6.1.1.4 of SP 800-56A Rev 3 and Appendix B.1.2 of FIPS 186-4 select the private key out of the range [1, q-1]. We used [2, q-1]. This distinction is unimportant. 0, 1, 2, 3, 4, etc. all make equally bad private keys. The defense against each of these is their negligible probability, not rejection sampling. Nonetheless, we may as well align with *some* specification, and NIST's formulation works fine. Change-Id: I33352061f3fbdbec5b14b576d15be98464a57536 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/62227 Commit-Queue: David Benjamin <davidben@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:
There are other files in this directory which might be helpful: