|author||David Benjamin <email@example.com>||Mon Sep 28 14:32:09 2020 -0400|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Wed Oct 14 17:49:56 2020 +0000|
Simplify 0-RTT tests. Add an earlyData and earlyDataRejected flag to configure the standard 0-RTT test options. It's too tedious otherwise. Along the way, I added an -expect-cipher flag to a few of the tests which could do with them. This does cause most 0-RTT tests to exchange a quick burst of data, so a few more fuzzer mode suppressions are needed. I think that's probably fine. Maybe we should mess with fuzzer mode so it's able to trial decrypt as this is getting a little tedious. Change-Id: Ib6490fe006d91294aab1a06d88f7793c6ae840c8 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/43086 Reviewed-by: Steven Valdez <firstname.lastname@example.org> Commit-Queue: David Benjamin <email@example.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: