aboutsummaryrefslogtreecommitdiff
path: root/src/crypto/tls/testdata/Client-TLSv12-ClientCert-RSA-RSA
diff options
context:
space:
mode:
authorFilippo Valsorda <filippo@golang.org>2018-11-03 20:04:44 -0400
committerFilippo Valsorda <filippo@golang.org>2018-11-12 20:43:06 +0000
commitdc0be727dc6182fb258f9f1048e9a9eef966c563 (patch)
tree8bd4399f0465e364a85a3456e64e0ad7fa5afdc5 /src/crypto/tls/testdata/Client-TLSv12-ClientCert-RSA-RSA
parentdb27e782780fcfe5da39671007374b06a4d8f2d4 (diff)
downloadgo-dc0be727dc6182fb258f9f1048e9a9eef966c563.tar.xz
crypto/tls: implement TLS 1.3 middlebox compatibility mode
Looks like the introduction of CCS records in the client second flight gave time to s_server to send NewSessionTicket messages in between the client application data and close_notify. There seems to be no way of turning NewSessionTicket messages off, neither by not sending a psk_key_exchange_modes extension, nor by command line flag. Interleaving the client write like that tickled an issue akin to #18701: on Windows, the client reaches Close() before the last record is drained from the send buffer, the kernel notices and resets the connection, cutting short the last flow. There is no good way of synchronizing this, so we sleep for a RTT before calling close, like in CL 75210. Sigh. Updates #9671 Change-Id: I44dc1cca17b373695b5a18c2741f218af2990bd1 Reviewed-on: https://go-review.googlesource.com/c/147419 Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Adam Langley <agl@golang.org>
Diffstat (limited to 'src/crypto/tls/testdata/Client-TLSv12-ClientCert-RSA-RSA')
0 files changed, 0 insertions, 0 deletions