|author||David Benjamin <firstname.lastname@example.org>||Tue Aug 20 15:55:24 2019 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Aug 22 15:43:08 2019 +0000|
Align 0-RTT and resumption state machines slightly QUIC is going to make this flow a bit more complicated, so let's simplify it a bit. The client flight states already know to skip themselves in 1-RTT resumption, so just run through the same states. Also remove a redundant early_data_offered check. (I think we originally skipped the states because we do half-RTT tickets and the transcript bits were precomputed.) Bug: 221 Change-Id: I3a62c864458012e74b46f7ef212abc125760c12d Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37144 Reviewed-by: Steven Valdez <email@example.com> Commit-Queue: David Benjamin <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: