commit | 522ad7e8fc8a90477643c136543c05186fb9ccf6 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Sat Jan 20 09:04:31 2018 -0500 |
committer | Adam Langley <agl@google.com> | Tue Jan 23 21:34:50 2018 +0000 |
tree | 26e49d3f15a7177cc107e4b2f03bf07c95fdbba2 | |
parent | 338eeb0c4f5c9b11835db1fad0de1fa0274ce71e [diff] |
Use EC_SCALAR for compute_wNAF. Note this switches from walking BN_num_bits to the full bit length of the scalar. But that can only cause it to add a few extra zeros to the front of the schedule, which r_is_at_infinity will skip over. Change-Id: I91e087c9c03505566b68f75fb37dfb53db467652 Reviewed-on: https://boringssl-review.googlesource.com/25147 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: