Google to offer encrypted search next week
news.cnet.com
news.cnet.com
Google has multiple data centers, dedicated caching and web clusters, complex internal network routing and load-balancing, etc. Then there's stuff like javascript and image hosting optimizations that you've got to make sure work without triggering SSL warnings across thousands of servers. Enabling SSL support for something like Googe search could potentially touch tens of thousands of systems. In short, maybe it's as simple as flipping a bit to enable SSL on the web farm, but I doubt it. There's probably a massive amount of internal engineering and organization behind the change, and that cost is what you're neglecting.
To give you perspective, it's trivial to enable SSL on a single-box website; it can be done in an afternoon. When we turned it on at Justin.tv, it took a few days (let's call it a week) of initial work, and ongoing maintenance costs to make sure that SSL sessions weren't breaking as we made improvements across the site. The costs go up as you get bigger and more complicated.
- You need a cert for example.com, and maybe a wildcard cert for .example.com, and for any additional levels of subdomains such as *.{x,y,z,etc}.example.com.
- Not all search engines seem to credit links to http://example.com/ and https://example.com equally.
- Even modern browsers sometimes abort downloads over SSL silently, without even an indication to the user that the download failed (despite sending a content-length header.) That's the really frustrating one.
I also use Google search for package tracking, and it's nice to get the numbers out of the search history instead of the merchant's site.
I know everyone wants to think that Google is collecting this information so that they know who to come for first when they take over the world... but it's also possible that the feature exists simply because it's useful.
It also breaks the shared-hosting model: your entire HTTP stream is encrypted, which means that key negotiation occurs before the server has your HOST header. This, in turn, means that the TCP/IP data (IPs and ports) are the only pieces of information that the server can use to determine which certificate to use. In practice, this means that a server can only host multiple distinct sites if it has multiple distinct IPs.
There's also the issue that some browsers (Firefox, I'm looking at you) do their best to scare users about self-signed certificates, which means that you need to pay for a cert.
Firefox is absolutely in the right, here. Self-signed certificates are worthless; if you'd like a free certificate, use StartCom or CACert. It also breaks the shared-hosting model: your entire HTTP stream is encrypted, which means that key negotiation occurs before the server has your HOST header.
This is only true for older servers; modern TLS implementations support name-based certificate negotiation.https://cacert.org gives a big fat warning in chrome.
If you need to support the general public, pay the $20 or whatever for a certificate with a widespread root.
http://en.wikipedia.org/wiki/Server_Name_Indication
http://en.wikipedia.org/wiki/Transport_Layer_Security#Suppor...
Its a shame they couldn't do it because customers have been asking for it.
On the other hand, the Chinese government might just ban Google search outright for such a move, although they haven't done this for GMail yet.
They could still force the issue and mandate that their CA be patched back in on all computers sold in mainland China.
Either case seems very unlikely, just outright blocking things they don't like seems to be their current approach. I don't see why they'd change that for Google.
This really is google just playing their cards at the right time and cashing in on the current privacy bandwagon in the media, casting themselves in a positive light. It doesn't alleviate any real privacy issues, whatever they are, with google.
There isn't a downside for us users - it's a good option for google to provide - it will cost them money in infrastructure, and will slow down the user experience by a significant factor - (you might not thing a half second matters, but it does, and google knows this - so this is possibly a convenient time for them to introduce this feature while people are focused on WHY privacy is important)
"Clients SHOULD NOT include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol."
I wonder if Google will implement POST forms instead of GET to prevent caching of request-uri data by the browser as well as proper Cache-Control/Pragma/Expires headers to prevent caching of search results.
ok, and most search results you click on will take you somewhere not secure. There may be little value add here.
From re-reading this article, it actually contains no value expect the headline itself. cnet should start just doing tweets instead of bothering to try to fill a page.
How do you think the Chinese government will like this? Or any government who attempts to censor searches? How will they know what's being searched for? Also, a lot of value can be gleaned from just the results, and not all lead to insecure sites.
As to China: I think China will block https search on Google. I think any government that censors search will block https search on Google. Playing the China card on this new feature isn't interesting. Google and/or the press should not try to score points through inflammatory China comments with this new feature rollout. Https search should be added simply because its a feature users want; and I'm sure some do.
Maybe it's just another feature that makes google the best search provider. If they don't do it, someone else will.