Go to file
David Benjamin c5f0c16b61 Restore ios64_compile to the CQ.
See if it works now that
https://boringssl-review.googlesource.com/c/16150/ is in.

Change-Id: I082f4826d1a2d8688664ce2f24a5ad561e4c41c4
Reviewed-on: https://boringssl-review.googlesource.com/16204
Reviewed-by: Steven Valdez <svaldez@google.com>
2017-05-11 16:49:08 +00:00
.github
crypto crypto/fipsmodule: Make more Known Answer Tests breakable. 2017-05-10 18:36:00 +00:00
decrepit Move des/ to crypto/fipsmodule/ 2017-05-02 19:21:02 +00:00
fipsoracle fipsoracle: Remove fax sample verification baked into test suites. This is covered by run_cavp.go. 2017-05-04 22:10:37 +00:00
fuzz Refresh fuzzer corpus. 2017-05-10 17:06:02 +00:00
include/openssl Add a flag to toggle the buggy RSA parser. 2017-05-10 15:49:33 +00:00
infra/config Restore ios64_compile to the CQ. 2017-05-11 16:49:08 +00:00
ssl Improve TestConfig flags for initial and resumption connections. 2017-05-09 21:14:28 +00:00
third_party Clear the last GTest warning suppression. 2017-02-16 19:03:32 +00:00
tool Make -loop survive errors. 2017-04-17 13:51:18 +00:00
util Add an option to build libFuzzer from DEPS. 2017-05-10 22:12:32 +00:00
.clang-format
.gitignore Add an option to build libFuzzer from DEPS. 2017-05-10 22:12:32 +00:00
API-CONVENTIONS.md Fix API-CONVENTIONS.md typos. 2017-01-04 01:46:32 +00:00
BUILDING.md Add the start of standalone iOS build support. 2017-04-07 17:13:44 +00:00
CMakeLists.txt Add an option to build libFuzzer from DEPS. 2017-05-10 22:12:32 +00:00
codereview.settings
CONTRIBUTING.md Add a CONTRIBUTING.md file. 2016-02-10 21:38:19 +00:00
FUZZING.md Fix FUZZING.md typo. 2017-03-30 16:54:18 +00:00
INCORPORATING.md
LICENSE
PORTING.md Restore SSL_CTX_set_ecdh_auto compatibility hook. 2017-03-14 14:54:45 +00:00
README.md
STYLE.md Work around language and compiler bug in memcpy, etc. 2016-12-21 20:34:47 +00:00

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: