| commit | a051bdd6cdc8fb7209e4339d6331fdd322be67f4 | [log] [tgz] |
|---|---|---|
| author | Brian Smith <brian@briansmith.org> | Wed Feb 03 21:12:37 2016 -1000 |
| committer | David Benjamin <davidben@google.com> | Tue Feb 09 16:21:41 2016 +0000 |
| tree | 0cf88096e021235346415c6c3fe48b09ec7545f1 | |
| parent | 767e1210e082df98a9a5846dc5c65db6cd4bfdb3 [diff] |
Remove dead non-|BN_ULLONG|, non-64-bit-MSVC code in crypto/bn. It is always the case that either |BN_ULLONG| is defined or |BN_UMULT_LOHI| is defined because |BN_ULLONG| is defined everywhere except 64-bit MSVC, and BN_UMULT_LOHI is defined for 64-bit MSVC. Change-Id: I85e5d621458562501af1af65d587c0b8d937ba3b Reviewed-on: https://boringssl-review.googlesource.com/7044 Reviewed-by: David Benjamin <davidben@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: