{"id":3114,"date":"2011-05-20T17:24:59","date_gmt":"2011-05-20T16:24:59","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=3114"},"modified":"2015-09-09T19:37:13","modified_gmt":"2015-09-09T11:37:13","slug":"google-proposes-way-to-speed-up-ssl-handshake","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2011\/05\/google-proposes-way-to-speed-up-ssl-handshake\/","title":{"rendered":"Google Proposes Way To Speed Up SSL Handshake"},"content":{"rendered":"

I’m always interesting when it comes to cryptography<\/a> and cryptographic trickery. We all know, the main problem with SSL<\/a> is speed – it can really slow your surfing experience down and for most people it annoys them enough to just not use it.<\/p>\n

Google researchers claim they’ve devised a way to reduce that painful wait when visiting an SSL encrypted site. Now, it may be faster but is it any less secure? You’d have to run through the paper to ascertain that.<\/p>\n

And well it can only work in a few very specific sets of circumstances, it’s not like it’s really going to change anything on a large scale.<\/p>\n

Google researchers say they’ve devised a way to significantly reduce the time it takes websites to establish encrypted connections with end-user browsers, a breakthrough that could make it less painful for many services to offer the security feature.<\/p>\n

What’s more, the technique known as False Start requires that only simple changes be made to a user’s browser and appears to work with 99 percent of active sites that offer SSL, or secure sockets layer, protection.<\/p>\n

“We implemented SSL False Start in Chrome 9, and the results are stunning, yielding a significant decrease in overall SSL connection setup times,” Google software engineer Mike Belshe wrote in a blog post published Wednesday. “SSL False Start reduces the latency of a SSL handshake by 30%. That is a big number.”<\/p>\n

The finding should come as welcome news to those concerned about online privacy. With the notable exceptions of Twitter, Facebook, and a handful of Google services, many websites send the vast majority of traffic over unencrypted channels, making it easy for governments, administrators, and Wi-Fi hotspot providers to snoop or even modify potentially sensitive communications while in transit. Companies such as eBay have said it’s too costly to offer always-on encryption.<\/p>\n

The Firesheep extension introduced last year for the Firefox browser drove home just how menacing the risk of unencrypted websites can be.<\/p><\/blockquote>\n

There’s a blog post about the speed improvements here:<\/p>\n

SSL FalseStart Performance Results<\/a><\/p>\n

It shows an approximate 30% reduction in the overall SSL connection setup time. They say they have implemented it in Chrome<\/a> 9 (the current public release of Chrome is version 11) – so that makes me wonder has it been running in Chrome since February this year when 9 was released?<\/p>\n

If you did want to disable it you can do so with the following command line option:<\/p>\n

--disable-ssl-false-start command-line<\/pre>\n