|author||David Benjamin <email@example.com>||Sat Jan 20 10:45:47 2018 -0500|
|committer||Adam Langley <firstname.lastname@example.org>||Tue Jan 23 22:04:58 2018 +0000|
Unwind total_num from wNAF_mul. The EC_POINTs are still allocated (for now), but everything else fits on the stack nicely, which saves a lot of fiddling with cleanup and allocations. Change-Id: Ib8480737ecc97e6b40b2c05f217cd8d3dc82cb72 Reviewed-on: https://boringssl-review.googlesource.com/25150 Reviewed-by: Adam Langley <email@example.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: