False Start: past time to fix your servers (31 Aug 2011)
A year ago I wrote about False Start in Chrome. In short: Chrome cuts the TLS handshake short to save a round trip in a full handshake. Since then we've posted results that show a 30% drop in SSL handshake latency.
When we enabled False Start by default in Chrome, we also included a list of the very small number of incompatible sites. This list was built into the browser in order to avoid breaking these sites. (See the original post for the reasoning.)
For some time I've been randomly eliminating chunks of that list. Mostly it's been the case that sites have already upgraded. I don't think that they did so specifically with False Start in mind, but that it was just a regular maintainance.
But it's now time that all sites are updated because the list is fading away fast:
- If you run A10 SSL terminators, ensure that you have firmware >= 2.4.3-p4
- If you run Brocade SSL terminators, ensure that you have firmware >= 10.2.01y
- If you run F5 SSL terminators, you need to be running the native SSL stack (which is the default, as opposed to the `compat' stack)
- If you run FTMG SSL terminators, you need Service Pack 2