th5/_dev
Filippo Valsorda f3fe024dc7 crypto/tls: do not drain 0-RTT data on Close
There is no reason a server can't just send a CloseNotify in its first
flight, and then close the connection without reading the 0-RTT data.

Also, it's not expected of Close to block on reading, and interlocking
with a Read can cause a deadlock.

Fixes NCC-2016-001
2017-09-05 21:06:34 +01:00
..
bogo crypto/tls: implement TLS 1.3 server PSK 2017-09-05 21:06:34 +01:00
boring crypto/tls: implement TLS 1.3 server PSK 2017-09-05 21:06:34 +01:00
caddy tris: import go wrapper and interoperability tests 2017-09-05 20:29:43 +01:00
mint tris: fix mint interop 2017-09-05 21:06:34 +01:00
picotls tris: add picotls interop 2017-09-05 21:06:34 +01:00
tris-localserver tris: fix NSS 0-RTT interop 2017-09-05 21:06:34 +01:00
tstclnt crypto/tls: do not drain 0-RTT data on Close 2017-09-05 21:06:34 +01:00
.gitignore tris: import go wrapper and interoperability tests 2017-09-05 20:29:43 +01:00
go.sh tris: fix cross-compilation and relocation 2017-09-05 21:06:34 +01:00
interop.sh crypto/tls: implement TLS 1.3 server 0-RTT 2017-09-05 21:06:34 +01:00
Makefile tris: fix cross-compilation and relocation 2017-09-05 21:06:34 +01:00