commit | 61ae41f198cd8e8aeaa4be04c546a3f132f25678 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Thu May 04 13:50:39 2017 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu May 04 19:16:48 2017 +0000 |
tree | 6b744ebd9bb31c901000f40b1dc96c81ec409486 | |
parent | a3d9c39c06db126b11c436536a76a5b401da9f89 [diff] |
Use a minimal totient when generating RSA keys. FIPS 186-4 wants d = e^-1 (mod lcm(p-1, q-1)), not (p-1)*(q-1). Note this means the size of d might reveal information about p-1 and q-1. However, we do operations with Chinese Remainder Theorem, so we only use d (mod p-1) and d (mod q-1) as exponents. Using a minimal totient does not affect those two values. This removes RSA_recover_crt_params. Using a minimal d breaks (or rather reveals an existing bug in) the function. While I'm here, rename those ridiculous variable names. Change-Id: Iaf623271d49cd664ba0eca24aa25a393f5666fac Reviewed-on: https://boringssl-review.googlesource.com/15944 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
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.
There are other files in this directory which might be helpful: