tree a8b323ac20148d4a8ef0bbce6b2ccbae828fc6dd
parent 6be491b7bb57c3950d4fbb97fdd4a141e3fa4d63
author David Benjamin <davidben@google.com> 1572547838 -0400
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1572549603 +0000

Discard user_canceled alerts in TLS 1.3.

Warning alerts do not exist in TLS 1.3, but RFC 8446 section 6.1
continues to define user_canceled as a signal to cancel the handshake,
without specifying how to handle it. JDK11 misuses it to signal
full-duplex connection close after the handshake. As a workaround, skip
user_canceled as in TLS 1.2. This matches NSS and OpenSSL.

Bug: b/135941563
Change-Id: I7ef546f1f166741b9f112686c75e6757331948f0
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38605
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Reviewed-by: Adam Langley <agl@google.com>