|author||David Benjamin <firstname.lastname@example.org>||Fri Dec 01 13:05:12 2017 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Dec 04 21:20:46 2017 +0000|
Add an option for False Start without ALPN. We can probably do this globally at this point since the cipher requirements are much more restrict than they were in the beginning. (Firefox, in particular, has done so far a while.) For now add a flag since some consumer wanted this. I'll see about connecting it to a Chrome field trial after our breakage budget is no longer reserved for TLS 1.3. Change-Id: Ib61dd5aae2dfd48b56e79873a7f3061a7631a5f8 Reviewed-on: https://boringssl-review.googlesource.com/23725 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: Adam Langley <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <firstname.lastname@example.org>
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: