|author||David Benjamin <firstname.lastname@example.org>||Mon Dec 25 10:10:43 2017 -0500|
|committer||Adam Langley <email@example.com>||Mon Jan 08 19:40:21 2018 +0000|
Make EC_POINT_set_compressed_coordinates_GFp use BIGNUM directly. All the messing around with field_mul and field_sqr does the same thing as calling EC_GROUP_get_curve_GFp. This is in preparation for ultimately moving the field elements to an EC_FELEM type. Where we draw the BIGNUM / EC_FELEM line determines what EC_FELEM operations we need. Since we don't care much about the performance of this function, leave it in BIGNUM so we don't need an EC_FELEM BN_mod_sqrt just yet. We can push it down later if we feel so inclined. Change-Id: Iec07240d40828df6b7a29fd1f430e3b390d5f506 Reviewed-on: https://boringssl-review.googlesource.com/24686 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: