commit | 0a5f00673656b1f8714f5ef275816e23fdf927f1 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Thu Nov 16 21:18:08 2017 +0800 |
committer | Adam Langley <agl@google.com> | Mon Nov 20 18:32:30 2017 +0000 |
tree | 1945f943e07a5233d3f6b4ad889ac67c66100d79 | |
parent | e7c95d91f8f42b0f17fb113e2204e2d9af4d2814 [diff] |
Test that EC_POINT_mul works with the order. |EC_POINT_mul| is almost exclusively used with reduced scalars, with this exception. This comes from consumers following NIST SP 800-56A section 5.6.2.3.2. (Though all our curves have cofactor one, so this check isn't useful.) Add a test for this so we don't accidentally break it. Change-Id: I42492db38a1ea03acec4febdd7945c8a3933530a Reviewed-on: https://boringssl-review.googlesource.com/23084 Reviewed-by: Adam Langley <agl@google.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: