| commit | 851943277fcbc6597d0d9d06f897e20b88afc32b | [log] [tgz] |
|---|---|---|
| author | Nick Harper <nharper@chromium.org> | Wed May 20 16:59:29 2020 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue May 26 16:31:02 2020 +0000 |
| tree | 693379a7483ab5666856d0ccb71093bfb0d0c4a7 | |
| parent | 9701e84eff26d0110d21f024debbab88d97e9c81 [diff] |
Modify how QUIC 0-RTT go/no-go decision is made. The previous implementation was too strict in its byte-for-byte equality check including Transport Parameters, because the Transport Parameters contain a field that QUIC requires be different on each connection. This change still has BoringSSL do a byte-for-byte check, but now it is only done over the quic_early_data_context. An additional requirement is imposed that the quic_early_data_context must be set for early data capable tickets to be issued. Bug: 295 Change-Id: I5145c10752b41908b6807c3a3c967653b0c13f37 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/41427 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.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.
Project links:
There are other files in this directory which might be helpful: