| commit | dc8b1abb75e41b4fdd6ae8dd57e67037d2f83efe | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Jan 20 18:55:47 2018 -0500 |
| committer | Adam Langley <agl@google.com> | Fri Feb 02 18:32:32 2018 +0000 |
| tree | bf8919915f2ba9e00c28ab4c7f71fb274802d54b | |
| parent | 43cf27e7d73426af6d94bc71d2aaa2d5526f1736 [diff] |
Do RSA sqrt(2) business in BIGNUM. This is actually a bit more complicated (the mismatching widths cases will never actually happen in RSA), but it's easier to think about and removes more width-sensitive logic. Bug: 232 Change-Id: I85fe6e706be1f7d14ffaf587958e930f47f85b3c Reviewed-on: https://boringssl-review.googlesource.com/25246 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.
There are other files in this directory which might be helpful: