commit | a9319d9b0f5d9cfe01ffd00ac926af86485dc981 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Jan 19 17:44:12 2021 -0500 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 19 23:17:12 2021 +0000 |
tree | 50fd3dc6a84dcd38243676d5bd7376e88c50607e | |
parent | 2f2d27eb5cd9106893d85d4109ffac4af928c685 [diff] |
Fix client 0-RTT handling with ALPS. When offering 0-RTT, the client should check that all carried-over values are consistent with its preferences. This ensures that parameter negotiation happens independently of 0-RTT. The ALPS version of this check was a tad too aggressive: a session without ALPS should be treated as always compatible. I'll follow this with a fix to the draft spec to clarify this. Change-Id: Ia3c2a60449c555d1d91c4e528215f8e551a90a9f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/45104 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@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: