|author||David Benjamin <firstname.lastname@example.org>||Sat Dec 30 00:33:54 2017 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Jan 08 20:03:42 2018 +0000|
Align various point_get_affine_coordinates implementations. The P-224 implementation was missing the optimization to avoid doing extra work when asking for only one coordinate (ECDH and ECDSA both involve an x-coordinate query). The P-256 implementation was missing the optimization to do one less Montgomery reduction. TODO - Benchmarks Change-Id: I268d9c24737c6da9efaf1c73395b73dd97355de7 Reviewed-on: https://boringssl-review.googlesource.com/24690 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: Adam Langley <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <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: