|author||Brian Smith <firstname.lastname@example.org>||Wed Oct 07 18:52:05 2015 -1000|
|committer||Adam Langley <email@example.com>||Tue Oct 27 16:38:25 2015 +0000|
Avoid hard-coded linkage of WNAF-based multiplication. If the application is only using the P-256 implementation in p256-64.c, then the WNAF code would all be dead code. The change reorganizes the code so that all modern toolchains should be able to recognize that fact and eliminate the WNAF-based code when it is unused. Change-Id: I9f94bd934ca7d2292de4c29bb89e17c940c7cd2a Reviewed-on: https://boringssl-review.googlesource.com/6173 Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: