commit | c4e4757b636b1765a322b76406e6d472e60b5f01 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Sat Mar 03 23:57:52 2018 -0500 |
committer | Adam Langley <alangley@gmail.com> | Fri Mar 30 19:53:52 2018 +0000 |
tree | 6b205ed9f0c9add97ed5e254a70e0f479a44dc0f | |
parent | a44dae7fd39a38cc8f0c20a9bc0a9f80e3742495 [diff] |
Make RSA key generation constant-time. This leaves RSA_check_key, which will be fixed in subsequent commits. Median of 29 RSA keygens: 0m0.220s -> 0m0.209s (Accuracy beyond 0.1s is questionable.) Bug: 238 Change-Id: I325f23fcc59302e68570908e5427b65471b799f6 Reviewed-on: https://boringssl-review.googlesource.com/26371 Reviewed-by: Adam Langley <alangley@gmail.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.
There are other files in this directory which might be helpful: