Go to file
David Benjamin 10443f5a6e Adjust comment on potential R^3 optimization.
It's doable, but a bit of effort due to the different radix.

Change-Id: Ibfa15c31bb37de930f155ee6d19551a2b6437073
Reviewed-on: https://boringssl-review.googlesource.com/25944
Commit-Queue: David Benjamin <davidben@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
Reviewed-by: Steven Valdez <svaldez@google.com>
2018-02-13 22:19:13 +00:00
.github
crypto Adjust comment on potential R^3 optimization. 2018-02-13 22:19:13 +00:00
decrepit Move OPENSSL_FALLTHROUGH to internal headers. 2018-01-29 18:17:57 +00:00
fipstools cavp_tlskdf_test.cc: include errno.h since errno is referenced. 2018-02-02 22:50:27 +00:00
fuzz Add a function which folds BN_MONT_CTX_{new,set} together. 2018-02-02 20:23:25 +00:00
include/openssl Fix threading issues with RSA freeze_private_key. 2018-02-09 22:17:11 +00:00
infra/config Revert "Add new bots to the CQ." 2017-10-09 21:38:10 +00:00
ssl Push an error if custom private keys fail. 2018-02-01 21:43:42 +00:00
third_party Add a tuned variable-time P-256 multiplication function. 2018-02-12 22:00:48 +00:00
tool Remove draft22 and experiment2. 2018-01-31 18:07:53 +00:00
util Handle directive arguments with * in them. 2018-02-02 19:59:06 +00:00
.clang-format
.gitignore [ndk] Change ndk deps in src and relocate to third_party/boringssl 2018-01-22 21:08:28 +00:00
API-CONVENTIONS.md
BUILDING.md Document the NDK's built-in toolchain file. 2017-12-14 01:54:47 +00:00
CMakeLists.txt Update tools. 2018-01-22 18:30:18 +00:00
codereview.settings
CONTRIBUTING.md
FUZZING.md
INCORPORATING.md
LICENSE Merge Intel copyright notice into standard 2018-02-12 21:44:27 +00:00
PORTING.md Add cpu-aarch64-fuchsia.c 2018-02-13 20:12:47 +00:00
README.md
sources.cmake Add a test for lots of names and constraints. 2017-09-20 19:58:48 +00:00
STYLE.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: