|author||David Benjamin <firstname.lastname@example.org>||Mon Oct 26 11:31:51 2015 -0400|
|committer||Adam Langley <email@example.com>||Mon Oct 26 19:47:26 2015 +0000|
Remove BN_MONT_CTX_init. One less exported function. Nothing ever stack-allocates them, within BoringSSL or in consumers. This avoids the slightly odd mechanism where BN_MONT_CTX_free might or might not free the BN_MONT_CTX itself based on a flag. (This is also consistent with OpenSSL 1.1.x which does away with the _init variants of both this and BIGNUM so it shouldn't be a compatibility concern long-term either.) Change-Id: Id885ae35a26f75686cc68a8aa971e2ea6767ba88 Reviewed-on: https://boringssl-review.googlesource.com/6350 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: