| commit | 21baf6421a7e1e03f85cf2243c3c2404f5765072 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Dec 08 17:12:38 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Dec 11 15:54:15 2017 +0000 |
| tree | 616b77bcde674a1d5d8a36e5ef1a283cca78664c | |
| parent | eb9232f06ffae855a9b8c5dfaffcaaf256dfbaac [diff] |
Fix CustomExtensions-Server-EarlyDataAccepted test. It's misnamed but, more importantly, doesn't do anything because the test client isn't sending early data to begin with. We really need to make these tests less error-prone to write. With this fix, the test actually notices if we remove the server-side 0-RTT check. Also remove MaxEarlyDataSize from the other server tests which erroneously set it. Any test with sets that was likely copy-and-pasted incorrectly. Change-Id: Idc24bc1590e0316946022341185285418ab8c77b Reviewed-on: https://boringssl-review.googlesource.com/23944 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: