kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
2,421 Commits 12 Branches 0 Tags 38 MiB
C 43.1%
C++ 23.5%
Go 13.6%
Raku 10.8%
Perl 4%
Other 4.9%
ef18746ad4
Go to file
Brian Smith ef18746ad4 Remove unused code for multiple-point ECC multiplication. 
The points are only converted to affine form when there are at least
three points being multiplied (in addition to the generator), but there
never is more than one point, so this is all dead code.

Also, I doubt that the comments "...point at infinity (which normally
shouldn't happen)" in the deleted code are accurate. And, the
projective->affine conversions that were removed from p224-64.c and
p256-64.c didn't seem to properly account for the possibility that any of
those points were at infinity.

Change-Id: I611d42d36dcb7515eabf3abf1857e52ff3b45c92
Reviewed-on: https://boringssl-review.googlesource.com/7100
Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 19:47:19 +00:00
.github Add a PULL_REQUEST_TEMPLATE. 2016-03-08 15:23:52 +00:00
crypto Remove unused code for multiple-point ECC multiplication. 2016-03-09 19:47:19 +00:00
decrepit Add |OBJ_NAME_do_all_sorted|. 2016-03-09 19:38:06 +00:00
fuzz Regenerate server_corpus and client_corpus. 2016-03-04 19:13:32 +00:00
include/openssl Add |OBJ_NAME_do_all_sorted|. 2016-03-09 19:38:06 +00:00
ssl Add an idle timeout to runner.go. 2016-03-08 22:26:41 +00:00
tool Pass |alice_msg| by reference in the SPAKE2 speed test. 2016-03-01 19:50:20 +00:00
util Add a script to run tests on Android. 2016-03-08 17:08:27 +00:00
.clang-format
.gitignore
BUILDING.md Enable upstream's ChaCha20 assembly for x86 and ARM (32- and 64-bit). 2016-02-23 17:19:45 +00:00
CMakeLists.txt Add 8bit-counters option for fuzzing. 2016-03-03 18:04:58 +00:00
codereview.settings
CONTRIBUTING.md
FUZZING.md Document how to minimise corpuses. 2016-03-03 18:05:34 +00:00
LICENSE Add some bug references to the LICENSE file. 2016-02-22 20:16:48 +00:00
PORTING.md
README.md
STYLE.md

README.md

BoringSSL

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: