Chrome's False Start lives up to its name: web security gets slower (but more compatible) in Chrome 20

false start google chrome

In 2010, Google claimed it had a way to significantly reduce the time it took to load encrypted websites, and in 2011, it proclaimed success: "False Start" reportedly reduced the latency of SSL handshakes for users of the Google Chrome browser by 30 percent. The only problem was that the company couldn't find a way to make it work with all such websites, only about 95 percent, and those that didn't work couldn't fail reliably enough that Google could add them to a blacklist or refused to fix their incompatibility. That's why Google security researcher Adam Langley announced that starting in version 20 of the Chrome browser, False Start will be turned off by default... and why the Google initiative will likely join the ranks of other tech industry in-jokes like Digital Rights Management and Microsoft Works.

The Verge
Log In Sign Up

Log In Sign Up

Forgot password?

We'll email you a reset link.

If you signed up using a 3rd party account like Facebook or Twitter, please login with it instead.

Forgot password?

Try another email?

Almost done,

By becoming a registered user, you are also agreeing to our Terms and confirming that you have read our Privacy Policy.



Choose an available username to complete sign up.

In order to provide our users with a better overall experience, we ask for more information from Facebook when using it to login so that we can learn more about our audience and provide you with the best possible experience. We do not store specific user data and the sharing of it is not required to login with Facebook.