tree 828d0c509c2f87ce5cb9e0a25500cd12a8a0caf4
parent 2de33c6b2bd882c58bfccec6617df775caeb76af
author David Benjamin <davidben@google.com> 1618260950 -0400
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1618334626 +0000

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>