4 ms·
The False Start blacklist, in case anyone else is curious: http://src.chromium.org/svn/trunk/src/net/base/ssl_false_start_blacklist.txt http://src.chromium.org/
by ivank 15y ago
The False Start blacklist, in case anyone else is curious: http://src.chromium.org/svn/trunk/src/net/base/ssl_false_start_blacklist.txt http://src.chromium.org/svn/trunk/src/net/base/ssl_false_sta... (about 4141 entries right now)
- wmf 15y agoLooks like Exchange and some SSL VPNs have a little standard compliance work to do.
- tptacek 15y agoFrom the TLS 1.2 RFC: The Finished message is the first one protected with the just negotiated algorithms, keys, and secrets. Recipients of Finished messages MUST verify that the contents are correct. Once a side has sent its Finished message and received and validated the Finished message from its peer, it may begin to send and receive application data over the connection. Hard to blame the servers for this.