Yahoo Encrypting Data In Wake of NSA Revelations
Nerval's Lobster writes "Following reports that the NSA aggressively targets Google and Yahoo servers for surveillance, Yahoo is working to encrypt much of the data flowing through its datacenters. 'As you know, there have been a number of reports over the last six months about the U.S. government secretly accessing user data without the knowledge of tech companies, including Yahoo,' Yahoo CEO Marissa Mayer wrote in a Nov. 18 blog posting. 'I want to reiterate what we have said in the past: Yahoo has never given access to our data centers to the NSA or to any other government agency.' In order to make Yahoo's systems more secure, she added, the company is introducing SSL (Secure Sockets Layer) encryption to Yahoo Mail with a 2048-bit key. That security measure will supposedly be in place by January 8, 2014. Beyond that, Yahoo plans on encrypting all information that moves between its datacenters by the end of the first quarter of 2014. Around that same time, the company will give users the option to encrypt all data flowing to and from Yahoo; it will also 'work closely with our international Mail partners to ensure that Yahoo co-branded Mail accounts are https-enabled,' Mayer wrote. (While it's not a crushing expense for massive companies such as Yahoo, introducing this sort of security does add to infrastructure and engineering costs, and takes time to actually put in place.)"
Not mentioned was which encryption schemes Yahoo is considering. Maybe it's simply HTTPS, but is that good enough? Are there other possibilities?
Since the NSA has backdoored encryption schemes in the past, how can Yahoo determine if the scheme they implement is actually going to prevent the NSA from decrypting it? It's a serious question, and you can patly answer "you can't", but if I were responsible for implementing this scheme, this is the question I would pose to the team and require some sincere digging because it would be an even bigger embarrassment to implement the encryption, and then read another Snowden-esque revelation showing it was for nothing, and I was made a fool of.
Sent from my ENIAC
Yahoo CEO Marissa Mayer wrote in a Nov. 18 blog posting. 'I want to reiterate what we have said in the past: Yahoo has never given access to our data centers to the NSA or to any other government agency.
The operative phrase here is "our data centers". A little less than half the data centers that Yahoo have their servers in are not owned by Yahoo, they lease space there. So, Yahoo's data flows in and out of the cage(s) they have their servers in into the house network. You can work it out from there.
Well, actually it's quite embarrassing that they're only doing this now...
Insert cat.
09 F9 11 02 9D 74 E3 5B - D8 41 56 C5 63 56 88 C0 45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
Strongly worded without PR-crafted terminology. Now, have you given these entities private information without a warrant?
I swear to God...I swear to God! That is NOT how you treat your human!
...if they can be forced to turn over encryption keys at the whim of some NSA/government authourity?
Entia non sunt multiplicanda praeter necessitatem.
>> encrypt all data flowing to and from Yahoo
BFD - since all the data is still sitting on servers somewhere, why would this offer any protection at all?
>> introducing this sort of security does add to infrastructure and engineering costs
BFW - welcome to 2008, Yahoo.
Whereas Google can. When I think cutting-edge technology and encryption Yahoo is the last company that comes to mind.
Doesnt do any good, if the law enforcement organizations (etc), have a warrant they can record all traffic from your IP/Phone. Depends on the company, but at AT&T Wireless they could turn on full sniffing from a mobiles internet traffic and record all TCP/UDP and even overlay it with location based service (tower strength triangulation). My boss said they had a group to assist in warrants, but after I setup the servers and routers, I NEVER saw an email, name or department identified, and I worked there for years setting up hardware from old packet data to 3G routers before I left.
So anyways, they record the entire SSL handshake so they can decrypt the session. You too can even try it for yourself in wireshark.
And who knows what is going on at the AT&T datacenters in those secret rooms...
That security is going to last as long as it takes to find one exploit against an endpoint that can be used to pull the key out of memory one time.
Let's be real about this -- if the N.S.A. wants data on any particular Yahoo user, or on all Yahoo users for that matter, it's not going to make one wit of difference if Yahoo encrypts its data or not. All the N.S.A. has to do is issue a national security letter, and Yahoo will cough-up whatever they got. Yahoo's encrypting the data on disk or in transit through their datacenters is little more than a pathetic attempt to lure customer's into believing that Yahoo is doing something to protect their data when, in fact, there's little Yahoo can do to prevent the N.S.A. for getting its hands on your data.
What about the talks about NSA being able to defeat SSL already?[1] [2]
I agree with someone who suggested one of the early pre-NSA encryption schemes.
You'd be better to roll your own, mind you. Remember, they already have your make files if you used Win 8 or Win 8.1, since it "indexes your local drive for fast search" which is a polite way of saying "spies on you".
-- Tigger warning: This post may contain tiggers! --
I love how so many people here are so sure the NSA can do magic on encryption... it's like complexity doesn't exist. They can solve any problem expressible in a general formal system! Halting problem? Fuck the halting problem, that's like stealing candy from a child.
NSA - the Chuck Norris of the agencies.
`echo $[0x853204FA81]|tr 0-9 ionbsdeaml`@gmail.com
It's not that we think the NSA can brute force SSL; we think the NSA has compromised the certificate authorities.
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
I just picked that comment because it said "thru [sic] ssl", and I interpreted as "breaking DH" or something. But I was referring to a somewhat spread sentiment that breaking encryption is just a matter of developing technique, which may not be the case (hence my sarcastic reference to the halting problem & Godel's incompleteness theorem).
Like this post above:
The issue is not whether they can brute force encryption.
We already assume they have the capability of brute forcing all encryption within a reasonable time frame. Something hilariously well protected? 3-6 months.
`echo $[0x853204FA81]|tr 0-9 ionbsdeaml`@gmail.com
if you change the code and lock them out?
Laughter is the Spackle of the Soul.
Yahoo mail's UI is horrific. Besides being ugly, if you have to enlarge text it becomes disuseful... It's a trainwreck of a UI.
Shoes for Industry. Shoes for the Dead.
I don't just blame the NSA for this situation. The providers are at fault for assuming that leased lines can be run unencrypted between their data centers because they're "private". Any time data enters or leaves a data center, one should assume it is being monitored. Everyone knows that's the most basic tenet of security.
But all these lazy vendors from Google to Yahoo and Microsoft and hundreds of others have taken the easy, lazy way out for years.
We all owe Snowden a big "Thank you" for kicking them all in the ass and getting them to do what they should have done in the first place.
I do not fail; I succeed at finding out what does not work.
I already had trouble understanding Marissa Meyer.
Have gnu, will travel.
+1 Insightful on the "government has the keys" point...
here it is: law enforcement & NSA must have the ability to access anything, given proper rights & proceedures
no one can make successful counter-point...all arguments are arguments over ***under what conditions*** the LE/NSA can access the information
Yahoo is doing absolutely nothing other than PR 'damage control' by manipulating the facts with this news.
Yahoo will give up **anyone's** data as fast as humanly possible when asked by a legal authority and this news changes nothing about that.
the speed at which LE/NSA can access our data under legal order is simply a **question of IT engineering**
Thank you Dave Raggett
All fun and games till your forced to hand over the SSL key and then all that encryption is pointless.
Normal Email is insecure by design. Yahoo cannot fix it. If you want to secure your email, then you got to do so at the end points, or quit using email.
Excuse me, but please get off my Pennisetum Clandestinum, eh!
If you secure your own inter-datacenter links, you accept only certs signed by your own private CA, hence the compromised CA is not a problem. And even if your private CA is compromised, ephemeral DH exchange ensures stored traffic remains difficult to decipher.
I remember the paranoid rantings of those in the FreeS/WAN community back in the day (that's IPSec software for Linux fyi) about needing opportunistic encryption support and DNS based keys so any two hosts on the Internet could communicate securely and prevent Big Brother from listening. ... "Its not paranoia if they really /are/ out to get you."
I also recall that I wished it would work, and set up my own hosts with it, but it never did work well and there just weren't enough participants to hit critical mass.
Thirdly I remember a quote from my old BBS days
- Michael T. Babcock (Yes, I blog)
The DH exchange only works if you don't get Man-in-the-Middled. Thats the point. Once the certificate authority is compromised, they can create a cert that makes them appear as the server you think you're supposed to talk to, so you do the DH exchange with their server, so the DH exchange isn't a problem. Then they just make another connection on to the destination which does a whole new DH exchange for keys.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
If you read me carefully, I referred to the status of stored traffic if the CA gets compromised.
http://xkcd.com/538/
This is NOT an issue with encryption.
This is an issue with a wrench. You can have it encrypted 5 different ways, but when the NSA comes a knocking, DEMANDING The data, and your alternative is to get shut down, go to jail, etc... guess what, they key's become suddenly available anyway.
Its another type of brute force encryption hacking that always succeeds. The RIAA and MPAA figured this out (mostly) long ago when they realized that from a technical standpoint it is a no win situation. At that point just let the government and/or courts solve the issue for you.
The NSA isn't going to crack any codes, they are going to ask for the keys, and if you don't give it to them they will destroy you.
howso?
FISA courts are there exactly for this right? Are you assuming the government is up to something or can you be specific?
I'm talking **current policy**
Thank you Dave Raggett
Wasnt there another story here about how the NSA cracks SSL? This story http://slashdot.org/story/13/10/30/1735257/nsa-broke-into-links-between-google-yahoo-datacenters