Re:False Start: Google proposal reduces SSL handshake to sin...
by ivank on Thursday May 19, 2011 @08:29PM
(#2565930)
The False Start blacklist, in case anyone else is curious: http://src.chromium.org/svn/trunk/src/net/base/ssl_false_sta... (about 4141 entries right now)
[ Parent
| on HN ]
Re:False Start: Google proposal reduces SSL handshake to sin...
by wmf on Thursday May 19, 2011 @08:49PM
(#2565973)
Looks like Exchange and some SSL VPNs have a little standard compliance work to do.
Re:False Start: Google proposal reduces SSL handshake to sin...
by tptacek on Thursday May 19, 2011 @09:50PM
(#2566082)
From 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.