Go to file
David Benjamin 2abda63a4f Fix TLS 1.3 variant fuzzers.
This was broken when we added the API to SSL.

Change-Id: I92d4330b0d70f655c9a9ad33898d6b84704e915c
Reviewed-on: https://boringssl-review.googlesource.com/17884
Reviewed-by: Steven Valdez <svaldez@google.com>
Commit-Queue: Steven Valdez <svaldez@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
2017-07-14 20:21:24 +00:00
.github
crypto Switch some pointer casts to memcpy. 2017-07-11 02:02:41 +00:00
decrepit Move des/ to crypto/fipsmodule/ 2017-05-02 19:21:02 +00:00
fipstools Have run_cavp.go create “resp” directories as needed. 2017-06-08 19:13:01 +00:00
fuzz Build the fuzzers with -Wno-missing-prototypes. 2017-07-14 20:10:47 +00:00
include/openssl Implement ContentType TLS 1.3 variant. 2017-07-14 19:48:00 +00:00
infra/config Restore ios64_compile to the CQ. 2017-05-11 16:49:08 +00:00
ssl Fix TLS 1.3 variant fuzzers. 2017-07-14 20:21:24 +00:00
third_party Fix build with VS 2017. 2017-06-07 18:56:06 +00:00
tool Implement ContentType TLS 1.3 variant. 2017-07-14 19:48:00 +00:00
util Remove ssl_{c,cc}_sources from generate_build_files.py. 2017-07-13 16:14:36 +00:00
.clang-format
.gitignore Add sde-linux64 to .gitignore. 2017-05-12 14:53:07 +00:00
API-CONVENTIONS.md Fix API-CONVENTIONS.md typos. 2017-01-04 01:46:32 +00:00
BUILDING.md Set static armcaps based on __ARM_FEATURE_CRYPTO. 2017-06-09 00:29:10 +00:00
CMakeLists.txt Fix linux_fuzz bot. 2017-07-14 15:39:31 +00:00
codereview.settings
CONTRIBUTING.md
FUZZING.md Fix typo in FUZZING.md. 2017-07-06 18:25:07 +00:00
INCORPORATING.md
LICENSE Add some bug references to the LICENSE file. 2016-02-22 20:16:48 +00:00
PORTING.md Restore SSL_CTX_set_ecdh_auto compatibility hook. 2017-03-14 14:54:45 +00:00
README.md
sources.cmake Implement scrypt from RFC 7914. 2017-06-12 20:32:21 +00:00
STYLE.md Add text about build logic to the style guide. 2017-07-06 01:38:28 +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: