|author||David Benjamin <email@example.com>||Mon Dec 25 14:35:33 2017 -0500|
|committer||Adam Langley <firstname.lastname@example.org>||Mon Jan 08 19:48:37 2018 +0000|
Fold away ec_point_set_Jprojective_coordinates_GFp. p224-64.c can just write straight into the EC_POINT, as the other files do, which saves the mess around BN_CTX. It's also more correct. ec_point_set_Jprojective_coordinates_GFp abstracts out field_encode, but then we would want to abstract out field_decode too when reading. That then allows us to inline ec_point_set_Jprojective_coordinates_GFp into ec_GFp_simple_point_set_affine_coordinates and get rid of an unnecessary tower of helper functions. Also we can use the precomputed value of one rather than recompute it each time. Change-Id: I8282dc66a4a437f5a3b6a1a59cc39be4cb71ccf9 Reviewed-on: https://boringssl-review.googlesource.com/24687 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: