Slashdot Mirror
Gmail Moves To HTTPS By Default
clone53421 writes "Although Gmail has long supported HTTPS as an option, Gmail announced their decision yesterday to switch everyone to HTTPS by default: 'We initially left the choice of using it up to you because there's a downside: https can make your mail slower since encrypted data doesn't travel across the web as quickly as unencrypted data. Over the last few months, we've been researching the security/latency tradeoff and decided that turning https on for everyone was the right thing to do.' I wonder if this has anything to do with the reports of Chinese users having their accounts hacked? 'Only two Gmail accounts appear to have been accessed, and that activity was limited to account information (such as the date the account was created) and subject line, rather than the content of emails themselves,' said David Drummond in that blog update. That does sound like it perhaps could be a result of insecure HTTP traffic being intercepted in transit between the users and Gmail's servers."
Encrypt everything.
I agree, and let me add I always thought Freenet's model was onto something. It's very failure proof and it caches static content. Which unfortunately is everything. But there's probably a way to get something wiki-like using the current message board implementation, providing one had an application that could interpret the data from a dedicated board.
How do you kill that which has no life?
OK, better late then never. Good that Google has finally introduced HTTPS as a default.
Now the next feature we all need is encryption of the content of our data when it is at rest on disks in Google's data center. That way even Google employees cannot read our mail. Not for serving up ads. Not for any reason whatsoever.
And after that, Facebook and Twitter...
Nah, I'm dreaming.
Anyone care to guess if Yahoo! will so the same thing?
I really hope so. I use a Yahoo account and I know how easy it is to sniff Ethernet. I hate to read mail at cafes and other places where I'm not certain of the LAN security.
Encryption has some overhead, but so what? It's not like modern hardware isn't up to it.
Anybody who cares about security has stopped using open protocols to send sensitive data. FTP is out, SFTP is in. Goodbye Telnet, hello SSH. And anybody who sends passwords over an open HTTP, SMTP, or IMAP connection is begging to be hacked. (POP? You're still using POP?) The issue is not security versus performance, it's the usual case of people not going to the trouble of upgrading their technology until they can't ignore the problem any more.
As usual, Google leads the pack in creating groundbreaking technology, and comes in dead last in dealing with the boring stuff, like dealing with security issues, or making sure you the resources to properly support your latest product. They need to hire fewer geniuses and start hiring more ordinary drudges with the patience to make things work in the real world.
I think is a common misconception to think that encrypted data cannot be compressed.
On Compression of Data Encrypted with Block Ciphers (from DCC2009, http://dx.doi.org/10.1109/DCC.2009.71).
From the article conclusions: "Simulation results indicate that, while still far from theoretical limits, considerable compression gains are attainable and improved performance can be expected as block sizes increase in the future."
Great move by Google,
Especially considering yahoo & hotmail don't have any option for https.
1a - If your email is encrypted with IPSEC, then there's a per-packet overhead from the extra packet header; it's not really a percentage, though you could think of it that way for average packet sizes. It's not significant for most applications except VOIP, which typically has very small data wrapped in lots of RTP/UDP/IPSEC/IP headers.
1b - If your email is encrypted at or above the transport layer, there's typically minimal overhead. The data encryption doesn't take extra space, except sometimes for the last packet of a session which might not contain a full block of plaintext so it gets padded by a few bytes.
1c - There's typically some setup overhead for key exchange. It doesn't take much transmission time unless you're on some funky very-low-bit-rate transmission medium, but there can be a couple of RTTs and some public-key math calculation time. So maybe it takes an extra second for you to start Gmail - big deal.
2 - That's why you compress the data *before* encrypting. Not many people use compressed transmission systems these days (e.g. fancy WAN optimizer tricks), and if anybody's still using SLIP or PPP with header compression, it doesn't care about HTTPS vs HTTP because that's not a Layer 1/2/3 problem.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
That access is actually provided in a ton of places you wouldn't expect.
Did you know that Xbox Live encrypts everything by default?
Did you know the one and only exception is... voice communication? Hmm...
Comment of the year
The day someone implements DNSSEC based server key delivery in a popular browser, there will be a grass-roots effort to make your dream come true.
I removed the Gmail gadget for iGoogle from my iGoogle homepage, because despite the iGoogle being loaded via HTTPS, the Gmail gadget would use plain HTTP.
Have they changed the Gmail Gadget to also use HTTPS? I couldn't find anything about it.
Edith Keeler Must Die
"Only two Gmail accounts appear to have been accessed"... by attacking Google systems directly. Using other methods, the attackers were highly successful.
Google disclosed that upon investigating users suspected of being attacked, they found "dozens" of Chinese human rights activists who had been compromised through phishing, malware or other systems that allowed security forces (presumably) to read their mail via a valid authentication. So, while Google itself may be mostly reliable on the backend, the security ecosystem as a whole is deeply flawed.
Google: "as part of this investigation but independent of the attack on Google, we have discovered that the accounts of dozens of U.S.-, China- and Europe-based Gmail users who are advocates of human rights in China appear to have been routinely accessed by third parties. These accounts have not been accessed through any security breach at Google, but most likely via phishing scams or malware placed on the users' computers."
http://googleblog.blogspot.com/2010/01/new-approach-to-china.html
So go change your passwords.
Is it obvious to everybody that encrypting everything is good only for privacy but doesn't seem to add much to security when compared to encrypting just the authentication data then using a session ID? Or rather, could the gurus please clarify where's the security increase in putting everything over https?
http://dilbert.com/2010-12-13
How big an effort is that to do in, say, WebKit? Firefox? Why isn't anyone working on it? Or are people? What are the benefits?
Forgive my ignorance, I truly didn't know. Is it something that a few thousand dollars of programming time would buy?
How do you effectively search your email history if it's all encrypted? Are there algorithms for indexing encrypted data without giving too much away?
I really want EVERY site I visit to use https. Why doesn't slashdot?
Just another "Cubible(sic) Joe" 2 17 3061
The standard e-mail addressing scheme for nearly all institutions is firstname.lastname@blahblah... It is most certainly valid.
Google just - being a service where anyone can register - wanted to ignore dots so that johnsmit@gmail couldn't impersonate john.smith@gmail and the other way around. In addition, google only allows a-z, . and 0-9, so you can't register john-smith@gmail, john_smith@gmail... etc... You actually need to have different letters and number combination than anyone else.
> Maybe that cert has been compromised by a Chinese insider.
i don't see mail.google.com's cert on any revocation lists, so it's probably ok.
given the approach google has taken in other aspects of the unfolding drama,
i think it's a fairly safe bet that it would've been revoked by now if there was any doubt that it may have been compromised.
Purge logs within a reasonable time since making the last octet of IP is not really making the log anonymous.
Do not store IPs in any of the search logs. I still have not figured out why Google does it. Aside from geographical information and abuse detection you can't really use IP anything, unless you want to provide information to authorities.
Expire Google cookie each week.
Provide an anonymous proxy with limited search capabilities. That way people who really care can get their top 10-20 results while the rest of us can enjoy more garbage and ads :)
Stop any self-sensoring. Information is out there to be free.
Put up information on how to make searches anonymous, e.g. how to use TOR, privoxy and other secure tools.
There is a free certificate authority: http://www.cacert.org/ . Unfortunately, it's not "official", but the root certificate is installed by default on a lot of free systems. (see ca-certificates package in Debian) I'm sure slashdot users are techy enough to understand it.
encrypted data doesn't travel across the web as quickly as unencrypted data
That just hurts my brain.
Actually, that is possible. Encrypted data doesn't generally compress as well as plaintext, and it's quite common for web servers to compress data before sending it to the client.
What, you think we're not doing it to them? Don't be naive. They just aren't honest enough to admit it.
But please do tone down the rhetoric. Nobody is being killed. Even knock on effects can't be called a "war".
We're all just chillin' here hk0ring each other's shti.
expandfairuse.org