tree e1dbb006dee59651e3c5cc225975f4d3e27573eb
parent 0ab86cf6f900a594187469ff5d546e5be203a480
author David Benjamin <davidben@google.com> 1517002392 -0500
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1517003607 +0000

Notice earlier if a server echoes the TLS 1.3 compatibility session ID.

Mono's legacy TLS 1.0 stack, as a server, does not implement any form of
resumption, but blindly echos the ClientHello session ID in the
ServerHello for no particularly good reason.

This is invalid, but due to quirks of how our client checked session ID
equality, we only noticed on the second connection, rather than the
first. Flaky failures do no one any good, so break deterministically on
the first connection, when we realize something strange is going on.

Bug: chromium:796910
Change-Id: I1f255e915fcdffeafb80be481f6c0acb3c628846
Reviewed-on: https://boringssl-review.googlesource.com/25424
Commit-Queue: Steven Valdez <svaldez@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
Reviewed-by: Steven Valdez <svaldez@google.com>