|author||David Benjamin <firstname.lastname@example.org>||Fri Nov 17 07:36:38 2017 +0800|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Nov 20 18:19:18 2017 +0000|
Run TLS 1.3 tests at all variants and fix bugs. We were only running a random subset of TLS 1.3 tests with variants and let a lot of bugs through as a result. - HelloRetryRequest-EmptyCookie wasn't actually testing what we were trying to test. - The second HelloRetryRequest detection needs tweaks in draft-22. - The empty HelloRetryRequest logic can't be based on non-empty extensions in draft-22. - We weren't sending ChangeCipherSpec correctly in HRR or testing it right. - Rework how runner reads ChangeCipherSpec by setting a flag which affects the next readRecord. This cuts down a lot of cases and works correctly if the client didn't send early data. (In that case, we don't flush CCS until EndOfEarlyData and runner deadlocks waiting for the ChangeCipherSpec to arrive.) Change-Id: I559c96ea3a8b350067e391941231713c6edb2f78 Reviewed-on: https://boringssl-review.googlesource.com/23125 Reviewed-by: Steven Valdez <email@example.com> Reviewed-by: David Benjamin <firstname.lastname@example.org> Commit-Queue: David Benjamin <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <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: