commit | d66bbf341351a25da701aa78b439ffcb4989c5a3 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Thu Nov 09 11:19:29 2017 -0800 |
committer | Adam Langley <agl@google.com> | Fri Nov 10 22:43:54 2017 +0000 |
tree | f1dafb9e13ddea63099e7dd6da316c6319d0c254 | |
parent | 607f9807e53efb22b56ed50b5eaa325a8afb865c [diff] |
Tidy up BN_mod_exp_mont. This was primarily for my own understanding, but this should hopefully also be clearer and more amenable to using unsigned indices later. Change-Id: I09cc3d55de0f7d9284d3b3168d8b0446274b2ab7 Reviewed-on: https://boringssl-review.googlesource.com/22889 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: