| commit | 794cc59e254665ad06e9b159d8b37dd46d2456bd | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Mar 25 22:24:23 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sun Mar 26 18:10:07 2017 +0000 |
| tree | f8ebc4686ace26d1c9338636c1cbb31dcdc318f7 | |
| parent | 02084ea3988446273558881a7e728b04d7338350 [diff] |
Send half-RTT tickets when negotiating 0-RTT. Once 0-RTT data is added to the current 0-RTT logic, the server will trigger a write when processing incoming data via SSL_read. This means SSL_read will block on transport write, which is something we've not tried to avoid far (assuming no renegotiation). The specification allows for tickets to be sent at half-RTT by predicting the client Finished. By doing this we both get the tickets on the wire sooner and avoid confusing I/O patterns. Moreover, we anticipate we will need this mode for one of the QUIC stateless reject patterns. This is tested by always processing NewSessionTickets in the ExpectHalfRTTData path on 0-RTT connections. As not other implementations using BoGo may not do this, this is configurable via the shim config. BUG=76 Change-Id: Ia0f56ae63f15078ff1cacceba972d2b99001947f Reviewed-on: https://boringssl-review.googlesource.com/14371 Reviewed-by: Steven Valdez <svaldez@chromium.org> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@chromium.org> Commit-Queue: David Benjamin <davidben@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: