commit | e2b7bb72216e88b8238083af63c3ecb244e79891 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon Apr 12 16:55:50 2021 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Apr 13 17:23:46 2021 +0000 |
tree | 828d0c509c2f87ce5cb9e0a25500cd12a8a0caf4 | |
parent | 2de33c6b2bd882c58bfccec6617df775caeb76af [diff] |
Only skip early data with HRR when offered. TLS 1.3 servers should only skip early data if the client offered it. Our HRR codepath didn't quite get this right. This CL is the minimal fix for this issue, but I think we should rearrange this logic slightly rather than deciding to do 0-RTT and then changing our mind. The next CL will do that. (This bug does not have any interoperability consequences. When configured to skip early data, we're happy to vacuously skip over zero early data records. We were just less strict than we should be.) Change-Id: Ida42134b92b4df708b2bb959c536580bec454165 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/46764 Reviewed-by: Adam Langley <agl@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: