News for hackers. Stuff that matters.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @08:28AM (#11454113)
EFF should stop with this silly scorecard. I hate the thing because it's inaccurate and incoherent (arguments I've made ad nauseam elsewhere on HN), but on this thread you can see another good reason: it makes EFF the ref, and crowds always try to work the ref.

So whatever "score" WhatsApp gets, it's the wrong score, because: not open source; because: runs on iPhones; because: metadata; because: Facebook is evil, &c.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by Findeton on Friday April 08, 2016 @08:40AM (#11454186)
But the point the EFF makes is very important. If the code is not open source, we just cannot verify the security of the application. All applications must be considered unsafe unless we can review the code. We can't review Whatsapp's source code, and therefore Whatsapp is to be considered unsafe.

So yeah, Whatsapp has made a probably positive move, but it is still largely unsafe.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by simonh on Friday April 08, 2016 @09:30AM (#11454482)
But if the code is open source, we _can_ verify it's security?

Heartbleed and Shellshock, the two most significant vulnerabilities found in heavily used open source software, were found by vulnerability testing and not code inspection. So while being open source is a nice-to-have attribute for a piece of software, that's as far as it goes. Painting open source as being a magical wand that wishes away all our security troubles is completely out of order.

Edit: I'll go further. It's become dismayingly apparent that very little systematic code review of open source software in order to secure it is actually taking place. It now seems quite possible that the most thorough investigations of software vulnerability, via code analysis or any other techniques, are carried out by those wishing to exploit them. They are well funded and highly motivated. Looked at in that light, the balance may well tip towards open source actually increasing the likelihood of software vulnerabilities being exploited maliciously.

The open source community has a long way to go if it's going to clearly demonstrate that it's model is advantageous, and complacent pronouncements of it's assumed superiority like this aren't going to achieve that.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by qznc on Friday April 08, 2016 @09:52AM (#11454628)
A verification of security is always based on an attacker model. There is no general security.

The actual point is not security, but trust and certainty. Being Open Source does not change whether some messaging app is secure or not. It changes our knowledge about the code. It also makes me have a little bit more trust in some company for revealing their stuff.

Even if WhatsApp open-sources the clients, there is still the problem of US jurisdiction. NSA can force them to silently including a backdoor or send everything to NSA-servers.

Trust is a difficult thing.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by lmm on Friday April 08, 2016 @10:57AM (#11455040)
> But if the code is open source, we _can_ verify it's security?

No - the code could be "open source" but unreadable. But if it's not open-source there's definitely nothing we can do.

> Heartbleed and Shellshock, the two most significant vulnerabilities found in heavily used open source software, were found by vulnerability testing and not code inspection. So while being open source is a nice-to-have attribute for a piece of software, that's as far as it goes

a) afl-fuzz and the like require access to the source code.

b) Those were the vulnerabilities that made it into production. They tell you nothing about what proportion of potential vulnerabilities were stopped by it being open source.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @12:46PM (#11456024)
Fuzzers do not require source code. That is absolutely false. Afl-fuzz does, but you badly overplayed your hand by adding "and the like". Fuzzing proprietary closed source protocols by instrumenting closed-source binaries is a bread-and-butter software security project that virtually any application security consultant can do effectively.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by JoachimSchipper on Saturday April 09, 2016 @12:17AM (#11459879)
And even afl has qemu-mode, although I have no idea how well that works.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by wglb on Friday April 08, 2016 @01:48PM (#11456492)
there's definitely nothing we can do.

This is very much not true. Understanding what any executable does is possible without the source code. In fact, if you are looking at the binary, you know exactly what you are dealing with, and don't have the doubt about what the build chain actually does with the source.

potential vulnerabilities were stopped by it being open source.

This presumably comes from "many eyes make all bugs shallow". But operationally this is not true, because there isn't really, except for rare circumstances, any useful review.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by simonh on Friday April 08, 2016 @12:29PM (#11455905)
Thanks for the correction regarding ali-fuzz, I wasn't aware of that. Unfortunately I can't update my post to fix that anymore.

I think this doesn't fundamentally change my point though. ali-fuzz was used to find shellshock, but that vulnerability had been in bash for decades. If it had ben found and closed within months of being introduced I'd be cheering the advantages of open source with the best of them, but that's decades during which a bad actor could theoretically have found and exploited that vulnerability with impunity using code analysis. That's exactly what I mean by the balance of advantages versus disadvantages of open source being tipped the wrong way right now.

I'm not enemy of open source, far from it, I'm just arguing for an open and honest assessment of the situation. If open source is really going to be a genuine security advantage, there's an awful lot of work to be done to make it so. It's not going to happen spontaneously.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by lmm on Friday April 08, 2016 @12:47PM (#11456031)
> I'm not enemy of open source, far from it, I'm just arguing for an open and honest assessment of the situation. If open source is really going to be a genuine security advantage, there's an awful lot of work to be done to make it so. It's not going to happen spontaneously.

I don't think you've shown anything about relative vulnerability rates. I agree that there are massive problems with even major open-source projects, the general state of software security is terrible, and we have a lot of work to do on that front (starting with moving to memory-safe languages post-haste). But none of those things contradicts that open-source software is much more secure than closed-source software.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @12:48PM (#11456034)
You haven't yourself empirically established that open source software is more secure, so you should be less smug about the logic you're using here.

In reality, software security is a function of the amount of expert attention that has been paid to a given piece of software. Popular open source software attracts a certain, stochastic, significant amount of attention, but money buys a more reliable amount of attention. There is insecure open source and secure open source, insecure closed source and secure closed source. Open source is a red herring.

There's a reason why, for instance, Firefox had Bleichenbacher's E=3 vulnerability, while IE didn't.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by baby on Friday April 08, 2016 @12:25PM (#11455874)
note that Heartbleed was not discovered via fuzzing.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by dave2000 on Friday April 08, 2016 @11:53AM (#11455572)
"The open source community has a long way to go if it's going to clearly demonstrate that it's model is advantageous"

How is it less safe than not having the source, though? Absent the source, how can you trust that the once trustworthy, if secret, code hasn't been nobbled via hackers, a court order etc.

The model of security through obscurity is what's broken, and that's what we've got here. You have to trust Facebook today, and forever and trust anyone else with the technical or legal power to silently violate its security; something that's much harder if the code is available for analysis.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @11:57AM (#11455615)
It's not less safe to have the source code. Source code is a good thing. All things being equal, I prefer open source components too. But all things are not equal.

In this case, if you're ideologically attached to open source, you're in luck: the cryptographic components WhatsApp uses are open source, and there's another good messenger that uses them: Signal, by Open Whisper Systems.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by dave2000 on Friday April 08, 2016 @03:29PM (#11457225)
The problem with WhatsApp is that IT is not open source, so you only have facebook's say-so that they're using the signal code, and you have to have faith that they've implemented it securely, and you have to trust that, as an american company, the current or future government won't silently compel them to introduce a weakness, such as allowing that when a phone gets the message `sing` it sends an encrypted copy of the last n messages back to facebook. I'd be more comfortable using the compilable, open source signal app, because i at least have the opportunity to see what the code is doing, should i somehow manage to find an sabotaged version of clang, gcc, vs etc.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @05:14PM (#11458033)
People need to stop writing this exact comment. Even if you're right about open source and security, you can't be right about it for this reason, because this comment is false.

You are not in fact stuck with Facebook's "say-so" about what WhatsApp is doing. Obviously, if you have the executable binary, you can straightforwardly validate its functionality with a disassembler/decompiler. There are thousands of people that do this professionally.

There might be some other reason why it's important that WhatsApp's code be published, but it can't possibly be this one.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by antihero on Tuesday April 12, 2016 @02:52AM (#11477685)
Has anyone actually done this? I lack the skill to but for a piece of software this important, surely someone is working on this? And will it be repeated for every update?

Personally if I was the NSA or GCHQ I think it would be a wicked smart plan to release this and have it be actually secure, have it audited, gain trust, let people use it for a while then after a while release an update that shoved all the messages in memory to a server somewhere once people let their guard down. Implausible yes, but that's the issue with trust. And I'm not sure releasing the clean source would really help this. The only thing would be to hold up on updating the app until a trusted party had audited the updated binary. More paranoia: Also would have to audit the specific binary for every country with wierd laws (e.g. UK's RIPA) appstore to make sure we didn't get a nice local flavour of poison.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by simonh on Friday April 08, 2016 @12:53PM (#11456066)
If WhatsApp releases the code, how do you know that's the code they run their service on? Open source does _nothing_ with respect to the trust issue with third party services like WhatsApp or Facebook. It's completely orthogonal.

I was wrong about heartbleed, it was found through a source code analysis technique called fuzzing - decades after the vulnerability was introduced. That's decades during which source code analysis could have been used by bad actors to find the same vulnerability and exploit it.

Opening the code doesn't by itself eliminate the vulnerabilities. What it does do is fire the starting pistol on a race between black hats and white hats to find and either exploit or close the vulnerabilities. It's very much a two edged sword. So what we need is confidence that the white hats are winning that race.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by jb613 on Friday April 08, 2016 @06:16PM (#11458524)
"Opening the code doesn't by itself eliminate the vulnerabilities. What it does do is fire the starting pistol on a race between black hats and white hats to find and either exploit or close the vulnerabilities."

The race is more dependent on motivation than whether the code is open or closed. Often, blackhats are financially motivated (whether they themselves monetize the vulnerabilities directly - or they are hired-by/paid-for a 3rd party) - they factor in their return on investment (ROI). Open source merely makes their job easier but given enough motivation, they can and will find vulnerabilities in binaries, remote services, etc almost as easily.

One problem is that many people believe in "many eyes makes all bugs shallow". Numerous examples prove that assumption false. Is it because there is more financial interest in closed systems? ...or is it because in open systems people automatically assume that because it's open that someone else must have vetted it? (e.g. "if I'm interested in it, and thousands/millions are too, then it's highly likely some expert better than me already looked at")

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by dspillett on Friday April 08, 2016 @09:47AM (#11454594)
If the source is open you can verify/test both ways, if it isn't then you only have the external testing option.

The code being publicly available does not guarantee security but makes insecurity easier to find which on balance indirectly increases security.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by phosphore on Friday April 08, 2016 @11:21AM (#11455288)
"Rogues are very keen in their profession, and know already much more than we can teach them" said locksmither Alfred Charles Hobbs, who in 1851 demonstrated to the public how state-of-the-art locks could be picked, in response to concerns that exposing security flaws in the design of locks could make them more vulnerable to criminals. This quote is not less true today when applied to blackhats. Open source doesn't mean secure, but security trough obscurity is not a good security model.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by davexunit on Friday April 08, 2016 @12:12PM (#11455759)
>The open source community has a long way to go if it's going to clearly demonstrate that it's model is advantageous

Some in the open source community flout the "many eyes makes all bugs shallow" argument, but in the free software community we do not assert this. Part of security is transparency, and this means being able to read the source code, freedom 1. Free software is a prerequisite for secure software that a user can trust.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @12:18PM (#11455807)
I understand and respect the tenets of your religion, but I do not practice that religion myself.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by belorn on Friday April 08, 2016 @01:08PM (#11456185)
Be civil. Don't say things you wouldn't say in a face-to-face conversation. Avoid gratuitous negativity. - Hacker News Guidelines

If you are opening up for incivility, I doubt there is an end what people will start calling each other. Do you really want to go down that road?

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by davexunit on Friday April 08, 2016 @12:40PM (#11455978)
Thanks for being condescending.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @12:44PM (#11456004)
If it helps you understand where I'm coming from, while I do in fact admire the FSF's ethic of free software, more so than I admire "open source", as a practitioner in the field of cryptographic security I find FSF-style preaching about security to be intensely condescending as well.

More here:

https://news.ycombinator.com/edit?id=11455588

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by davexunit on Friday April 08, 2016 @12:48PM (#11456037)
The linked comment has NOTHING to do with what the FSF has said about software security.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by belorn on Friday April 08, 2016 @12:59PM (#11456108)
If you want to compare track records of close sources software with open source, we have IE6 and flash. We have windows 98 and XP. We have every snake oil product ever sold that the producer knew wasn't safe but sold anyway. Heartbleed and Shellshock were big bugs, but they did not create the concept of botnets nor was they so successful that they created a market where before there wasn't.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @01:04PM (#11456155)
So basically the theory here is that if you look back to software written in the mid-to-late 1990s, you tend to find insecure software.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by belorn on Friday April 08, 2016 @01:21PM (#11456265)
If you want to be like that, all of them were written mid-to-late 1990 or before it:

Bash was released in 1989 and initially development started some time before that.

OpenSSL project was founded in 1998.

Windows XP was initial developed in the late 1990s, released 2001.

Macromedia Flash 1.0 was released 1996 and initially developed a couple years before.

So should we only count software vulnerabilities that was created after 2010? 2016? What proof would satisfy you?

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @01:22PM (#11456278)
I'm really not sure what point you're trying to make here, because obviously both Bash and OpenSSL are poster children for the perils of legacy insecure software, and both are still in wide use --- far wider than Windows XP!
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by belorn on Friday April 08, 2016 @02:25PM (#11456776)
Are you confused by the parent argument that Heartbleed and Shellshock is proof that open source has the same likelihood of software vulnerabilities being exploited maliciously as closed software?

Or are you confused by your own argument that software written in the mid-to-late 1990s tend to be insecure software, and thus we should disregard that some software has been more exploited historically than others?

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @05:16PM (#11458046)
Neither. I think age has a lot to do with whether software is or isn't secure. Software written in the 1990s (or before) is unlikely to be secure. I think open/closed source has very little to do with security. Some open source software is secure, some isn't, and the same goes for closed-source software.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by kzhahou on Friday April 08, 2016 @12:15PM (#11455780)
When the source code has a whitelist of usernames for which encryption should be disabled, put there under court order, you'll see the difference between external verification vs source code inspection.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @12:19PM (#11455814)
I really think that's what most people arguing against WhatsApp believe: that a backdoor in a secure messaging application would take the form of intelligible source code expressing directly that backdoor.

Obviously, a WhatsApp backdoor would not in fact take that form.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by whyever on Friday April 08, 2016 @01:11PM (#11456207)
What would it look like?
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @01:16PM (#11456235)
A binary patch.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by kzhahou on Friday April 08, 2016 @01:58PM (#11456571)
Could be a number of things. Some might be visible only during build/packaging as you say, others visible in code.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @05:16PM (#11458053)
Why would anyone patch the source code when they can just as easily patch binaries?
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by geofft on Friday April 08, 2016 @10:44AM (#11454946)
"Open source" isn't quite the right term, but it's on the right track.

What you definitely don't need is permission to redistribute, modify, etc. the software. Those are important for user freedom, but for the goal of verifying that a particular app on a walled-garden app store does what it claims to do, those don't help you. You just need access to source code.

What you do need, whether or not you have source, is an understanding of what the software does. Sure, you can probably do this by disassembling the software. But if you can disassemble the software and understand it, there is nothing more that having the actual source would tell you. If the company is expecting that people will disassemble it to verify it, they might as well release source.

What you also need, given either source or a binary, is assurance that everyone else is running the same binary as you have. Given source, that probably requires reproducible builds and a documented and reasonable build chain. Given a binary, that requires some distribution mechanism that ensures that everyone in fact gets the same binary.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by agumonkey on Friday April 08, 2016 @02:53PM (#11456950)
> But if the code is open source, we _can_ verify it's security?

But if the code is not open source, we _cannot_ verify it's security?

Ability is already good. Not enough but necessary.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @05:17PM (#11458059)
Why do you believe that we _cannot_ verify its security?
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by agumonkey on Saturday April 09, 2016 @10:16AM (#11461307)
I mean closed sources are .. closed sources (did I say something stupid?). Unless you consider black box testings or things I don't know.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Saturday April 09, 2016 @04:11PM (#11463065)
The original source code is unavailable. But the assembly code that actually implements the program is not, and there are a variety of techniques reversers use to lift assembly into higher-level representations --- not that you'd need to in this case.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by pekk on Friday April 08, 2016 @10:07AM (#11454715)
Do you understand the concept of "necessary, but not sufficient"?
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by simonh on Friday April 08, 2016 @02:05PM (#11456626)
Yes I do, but that's not what the post I was responding to was saying. However I have not seen any arguments that convince me if its necessity. Furthermore were talking about third party services. What code they open sourcezsndcegat code they actually run on their servers are two different questions. Open source doesn't solve this problem whichever way you slice it.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by hiq on Friday April 08, 2016 @09:33AM (#11454501)
See this thread for tptacek's views on the topic:

https://news.ycombinator.com/item?id=11432047

In short, "sources do not guarantee anything, and it's better to inspect the binary directly".

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by kasey_junk on Friday April 08, 2016 @09:09AM (#11454359)
I don't think that open source is considered a requirement by the professional security community.

Which makes sense, we've known for a very long time that you can't trust the source, so you must verify the binary one way or the other.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by akvadrako on Friday April 08, 2016 @09:13AM (#11454390)
And one way to increase confidence in the binary is to compile it yourself.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by kasey_junk on Friday April 08, 2016 @09:15AM (#11454398)
Twice, using 2 different compilers. That you have also audited.

Or you could observe what the original binary actually does, which you need to do anyway.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @09:38AM (#11454535)
Exactly what I would expect to hear from an NSA stooge!
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by cptskippy on Friday April 08, 2016 @09:52AM (#11454625)
At which point you might as well just let someone else compile it and look at their binary.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by dave2000 on Friday April 08, 2016 @11:44AM (#11455490)
If you have the source then you can see what it does.

If you only have the binary you have no idea what it does. You can observe what it does today, but what use is that if tomorrow it receives a short message from Facebook which tells it to email back the encrypted, compressed copy of your messages it's been quietly keeping for the last few hours/days/weeks?

The argument "what about this or that open source project with bugs in it" is silly. It's an argument for more scrutiny of code, not blindly trusting in third party code where you have no idea if they can be trusted today, or in the future, or can be compelled to spy on you, or introduce weaknesses deliberately into their products. Open source mitigates against several of these risks.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by kasey_junk on Friday April 08, 2016 @11:59AM (#11455623)
> If you have the source then you can see what it does.

That is literally false. We have known from the 70s that you cannot know what an application will do from the source. I can't believe I'm actually having to reference "Reflections on Trusting Trust" but it is the entire point of one of the most seminal talks in our industry.

To defeat that style of attack you literally need 2 different compilers, I didn't pick that out of a hat, its also from the literature.

> If you only have the binary you have no idea what it does. You can observe what it does today, but what use is that if tomorrow it receives a short message from Facebook

Figuring out what a binary does without source is a very common task in our industry. I'm told there are people who do it for fun, and I know people that do it for money.

Regardless of whether you have the source or not, you have to verify the binaries behavior, both because of intentional trusting/trust attacks and for flaws that are non-obvious from the source.

I'm sure the source is helpful, and the source with repeatable builds is even better but its not a requirement nor does it seem to be a very high priority for the people that do this sort of work professionally.

>"what about this or that open source project with bugs in it"

I am certainly not making that argument.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by dave2000 on Friday April 08, 2016 @03:26PM (#11457193)
Yeah, it's all old news. I regularly use several different compilers so that's not such the shock you suspect it might be. Also, for your paranoia to be really effective you must also assume the disassemblers must also be in on the act.

You need the source to have even a crack at being sure there's no foul play. Trusting the current behaviour of an app now is no guarantee. Anyone could write an app which, when it receives a certain message at a certain time changes subtly its behaviour. If you had the source this wouldn't be possible (ok, it would be possible if someone's got at the app and all major compilers and disassemblers going back years and want to blow that little secret on this one exploit); you'd have a chance of seeing the logic.

If you don't have the source then you're no better off because you have all those risks plus you have no idea whether or not someone has good intentions but a poor testing regime, or a bad actor, or any number of other problems.

People who do security work successfully seem to be unanimous that you don't do your own security, and that you use open source solutions so you can see that people are doing what they say you are doing. And this is done in the name of reducing risk, by reducing the number of people you have to trust.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @05:18PM (#11458077)
Could you point out some of these "people who do security work"? I should like to meet one someday.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by PeCaN on Friday April 08, 2016 @12:15PM (#11455783)
> If you have the source then you can see what it does.

What if it exploits a compiler bug to do something different than it looks? What if the compiler recognizes the code and instruments it with its backdoor? Sure, GCC probably doesn't, but what if the code was meant for Windows and only builds under MSCV which you can't audit? What if the code exploits an undocumented “feature” in Intel x86 processors? What if it uses a backdoor in Intel's randomness hardware? Modern Intel processors have many undocumented features and essentially can do whatever the hell they want with your code. The NSA almost certainly has a backdoor in Intel's RDRAND[1]. x86(_64) is impossible to trust; even VIA CPUs may be compromised (though they lack the “management engine” of Intel and AMD—if I were to 100% audit a crypto-related program that only runs on x86, I would use a VIA system and intercept any instructions that use the hardware RNG).

Point is, open source makes some things vastly easier, but the point is you _need_ to audit the binary anyway. That's the _only_ way to trust it. You _cannot_ trust the source code. You cannot even trust a machine other than POWER, RISC-V, or SuperH/JCore.

If you're not going to be paranoid as all hell, auditing crypto is pointless.

1. http://arstechnica.com/security/2013/12/we-cannot-trust-inte...

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by dave2000 on Friday April 08, 2016 @03:33PM (#11457252)
You compile with various compilers and you decompile them with different decompilers. This is trivial today.

Randomness hardware? There are already perfectly good PRNG routines available as used by currently available strong encryption.

I understand the criticisms of just relying on the fact that something is open source but the alternative - closed source - has exactly 100% of those problems, plus a whole other lot of new ones too.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @05:18PM (#11458072)
"Perfectly good PRNG routines"? No, that is not at all true. Serious cryptographic software uses the OS's random number generator. There are not in fact "perfectly good PRNG routines" ready to take off the shelf and plug into crypto software.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by PeCaN on Saturday April 09, 2016 @04:04AM (#11460435)
> Randomness hardware? There are already perfectly good PRNG routines available as used by currently available strong encryption.

Yeah. How do you seed those with a good source of entropy? That's what RDRAND etc are for.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by danielrhodes on Friday April 08, 2016 @09:40AM (#11454553)
> it is still largely unsafe

It's not unsafe, you just don't know if it's safe or not. That doesn't make it unsafe.

Even if the code were open source and there were some guarantee that WhatsApp was using that exact code during compilation, you still would not know if it's safe. Just like most other people, you are relying on people experienced with such things to confirm that they are doing things in a "safe" way. Thus for all practical matters, it really doesn't matter if it's open source or not.

There is always going to be an unknown here, and open source does not reduce that much risk. In fact, it's probably better to look at how WhatsApp, the software, behaves (i.e. what it does on the wire) rather than the code. Sure there could be backdoors, but that is the risk you take when you use any pre-compiled software -- open source doesn't change that.

All we are really left with then is trust.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by lmm on Friday April 08, 2016 @11:00AM (#11455068)
> Even if the code were open source and there were some guarantee that WhatsApp was using that exact code during compilation, you still would not know if it's safe.

Speak for yourself

> Just like most other people, you are relying on people experienced with such things to confirm that they are doing things in a "safe" way. Thus for all practical matters, it really doesn't matter if it's open source or not.

If you rely on the experts then it still matters to you whether being open-source means more or better experts.

> In fact, it's probably better to look at how WhatsApp, the software, behaves (i.e. what it does on the wire) rather than the code.

It is provably impossible to tell whether the RNG has been backdoored that way.

> Sure there could be backdoors, but that is the risk you take when you use any pre-compiled software -- open source doesn't change that.

Huh? So you require reproducible builds and/or build from source yourself. You absolutely don't trust that some random binary is what it claims to be.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by danielrhodes on Friday April 08, 2016 @02:22PM (#11456752)
You may not realize it, but you have proven my point.

At what point does this all become totally impractical? Should you also manufacture your own chips as well to make sure there are no backdoors at the hardware level? How about for people who have no time for any of this (99.99999999% of the world)?

At some point, you need to trust somebody in this chain of dependencies.

People who are beating their drums about open source are in essence saying: trust no one. But in the real world, that is not realistic.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by lmm on Sunday April 10, 2016 @05:44PM (#11468319)
> Should you also manufacture your own chips as well to make sure there are no backdoors at the hardware level? How about for people who have no time for any of this (99.99999999% of the world)?

You should ensure that your supply deal allows you to audit the manufacturing, yes. Maybe you don't actually have the time or money to do so, but if they don't offer that capability that's a giant red flag.

> At some point, you need to trust somebody in this chain of dependencies.

You never trust any single party unconditionally. I mean sure, even if you get an audit done, your audit agency could be crooked - a sufficiently large conspiracy can defeat anything a single person can do by themselves. But you don't want to put yourself in the position where one rogue company - or even one rogue employee at that company - could entirely compromise your security. If that level of security is good enough, why even bother using encryption at all?

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by pookeh on Friday April 08, 2016 @10:04AM (#11454700)
And if you don't trust FB then it is ... unsafe :)
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by danielrhodes on Friday April 08, 2016 @10:57AM (#11455039)
Well if your point is that safe or unsafe are always subjective conclusions, then of course I agree with you. If the safe/unsafe determination is being declared as an objective conclusion, then I don't.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by n13 on Friday April 08, 2016 @09:05AM (#11454331)
Just wondering what EFF has to say about other Apps like Telegram since code is open sourced [1]?

[1] - https://telegram.org/apps#source-code

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by akvadrako on Friday April 08, 2016 @09:15AM (#11454394)
Telegram wouldn't fair very well. It has weak home-grown encryption and doesn't enable it be default.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by morsch on Friday April 08, 2016 @09:38AM (#11454534)
They've got two scores for Telegram on their score card[0]: "Telegram" scores poorly (4 out of 7), "Telegram (secret chats)" scores perfectly (7 out of 7). The quality of the encryption algorithm itself doesn't factor into it, though Telegram gets a check for having a recent audit.

Even if the crypto was good, the cognitive load of having to decide whether you want a chat to be secret or not makes it a bad choice IMO, especially if it comes with a downside.

[0] https://www.eff.org/secure-messaging-scorecard

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @09:50AM (#11454613)
7/7 being a score that no practicing crypto engineer would be likely to come up with for that application.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by yeukhon on Friday April 08, 2016 @11:30AM (#11455356)
If that's the stand, EFF is basically with Stallman that there shouldn't be any proprietary software and that view is hard to agree on.

> All applications must be considered unsafe unless we can review the code.

Let's face it. I like to give the liberty to people who prefer to keep their code secret and their responsibility to hire people to do proper security auditing. Curious whitehats are welcome to attack systems which have bounty program. While obfuscation is never a good idea in security, the paywall between Facebook and the public keeps large exploits away. Attacks came directly from behavior testing require some cleverness and dedication (of course there are those really dumb XSS everywhere). So in this case, obfuscation by hiding the source code is one way. However, you can argue that someone could have lost work laptop and steal the source code (let just assume some startup whose git repo is clonable entirely onto the laptop).

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by dcposch on Friday April 08, 2016 @09:18AM (#11454419)
You mixed some straw-man objections ("Facebook is evil") with one that's important and legitimate.

People are right to be cautious with closed source crypto. It has a long and sordid history of turning out to be snake oil, terribly implemented, or outright backdoored.

Given the people involved, though, and all the scrutiny the Axolotl protocol has already withstood, WhatsApp looks trustworthy.

It would be better if the source code were available for inspection, and even better if it had a deterministic build so that people vould verify that what's installed on their phone was actually built from that code.

Rolling out usable end-to-end encryption to a billion people is still a huge achievement and we owe Moxie, Trevor Perrin, and the whole WhatsApp and Open Whisper Systems teams our thanks.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by rmellow on Friday April 08, 2016 @08:40AM (#11454181)
The real victory for privacy here is that a tool used by the masses has given then end to end encryption, and that alone is a game changer:

- This enables network effects for private communication, i.e. it's harder for privacy to be breached by an insecure partner

- One can avoid being singled out for using an obscure tool to hide their communication

Sure, it doesnt fit all the marks EFF would desire, but it's undeniably a very positive achievement for privacy.

The only thing missing is a canary to signal some sort of back door, since it's not open source. Then again, diverting users away from their app is not in their interests.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by code_research on Friday April 08, 2016 @08:38AM (#11454170)
Please provide a link to a "scientific" but easy understandable comparison of crypto communication software that educates users about what is important to understand about this complicated issue. It would be great if you could motivate the crypto elite of the world to contribute to such a comparison site. Thanks!
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by ethbro on Friday April 08, 2016 @08:53AM (#11454252)
I think the problem is that crypto is a devil-in-the-details issue. I'll cast around and see if I can dig up a survey of the general divergences in crypto schemes, but one chink in an implementation sinks the ship.

Haven't dug into it, but I guess another interesting question would be "Are various crypto solutions using the same underlying base libraries (and versions) or each rewriting their own implementation of a new system?"

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by anonymousDan on Friday April 08, 2016 @08:46AM (#11454208)
Here's one for TextSecure: https://eprint.iacr.org/2014/904.pdf They claim doing the equivalent for WhatsApp is future work, although the paper is a year or two old.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @08:38AM (#11454175)
No. Just because you want it to exist or think it needs to exist, doesn't mean it actually exists.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by nailer on Friday April 08, 2016 @08:45AM (#11454207)
> No. Just because you want it to exist or think it needs to exist, doesn't mean it actually exists.

I understand the parent believes that the EFF are doing this already. I.e. suggesting that if the comment he's responding to doesn't like the EFF's approach they're welcome to create their own.

No thoughts either way but I'm pretty sure you misread them.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by CaptSpify on Friday April 08, 2016 @10:40AM (#11454921)
I don't follow what you mean. Because security can be improved for a product, means it shouldn't be pointed out? Sounds like that's more of a reason for a scorecard to exist?
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by nxzero on Friday April 08, 2016 @08:32AM (#11454135)
What then is good for the masses?
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @08:38AM (#11454172)
I like the idea of a three-tier threat model:

Tier 1: potentially inconvenient but maximally secure, in an OPSEC sense (PGP, for instance, though I would personally put Signal here too). Use carefully for security against state-level adversaries.

Tier 2: convenient mainstream applications with strong security but some tradeoffs. Your default choice, security against criminal adversaries. I'd put WhatsApp and iMessage here (but not many others).

Tier 3: unencrypted or dubiously encrypted mainstream applications, unsafe against any adversary, but potentially useful as an endpoint to (cautiously) bootstrap communications. Google Talk and AIM would go here for me.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by eru on Friday April 08, 2016 @08:46AM (#11454210)
PGP doesn't have plausible deniability. It actually has `you can prove anyone else what I said to you', if you sign anything. That's dangerous, so shouldn't be on tier 1.

(Or at least that's how it used to be.)

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @09:40AM (#11454544)
Most secure messengers don't have deniability.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by CaptSpify on Friday April 08, 2016 @10:37AM (#11454901)
So because most of them implement security wrong, we should just accept that as normal? I feel like I'm mis-understanding your point?
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @11:53AM (#11455570)
I definitely do not think adopting a new, unverified cryptosystem simply to get better "deniability" is a good tradeoff. I see the value, but it's not the most important thing to get right in a secure messenger.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by CaptSpify on Friday April 08, 2016 @01:34PM (#11456380)
> I definitely do not think adopting a new, unverified cryptosystem simply to get better "deniability" is a good tradeoff.

I agree, but I don't see how that's relevent. This could be added to pgp, without "adopting a new, unverified cryptosystem"

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by rschuetzler on Friday April 08, 2016 @09:01AM (#11454304)
Is plausible deniability something you want in your communication? Just curious, as this is something I haven't heard before. It seems like non-repudiation would be what you want in your comms.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by eru on Friday April 08, 2016 @09:15AM (#11454401)
See https://en.wikipedia.org/wiki/Off-the-Record_Messaging

Sometimes you want plausible deniability, sometimes you want to sign something for all the world to be able to verify.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by rschuetzler on Friday April 08, 2016 @09:32AM (#11454496)
Got it, thanks. I'd heard of OTR, but never really looked into what it meant. Makes sense now.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by nabla9 on Friday April 08, 2016 @09:24AM (#11454454)
In addition to tiers, I think there are dimensions. Mainly:

1: security against targeted surveillance from criminals or state-level adversaries. (= spying targets).

2: security against mass surveillance. (= finding targets)

I think it's possible to have Tier 2 system that is Tier 1 against mass surveillance. Individual connections don't have to be proofed against state level actor targeting individuals. It's enough that the whole system works in a way that makes mass surveillance too expensive.

In fact, I think this kind of security is enough to ease most concerns against government surveillance.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by nxzero on Friday April 08, 2016 @09:32AM (#11454495)
Right, key is to make it so expensive that the obsession over mass surveillance becomes economically unhealthy.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by antihero on Friday April 08, 2016 @09:09AM (#11454365)
Signal "runs on iPhones" which you've deemed to be a bad thing for some reason, so surely that should be tier 2 too. In fact, most things "run on iPhones" so it's kind of an odd argument. What's terrible about running on iPhones?
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by parasubvert on Friday April 08, 2016 @11:05AM (#11455118)
He was holding that up as a popular strawman argument, among the rest in that list.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @09:40AM (#11454548)
You misunderstood the point I was making.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by antihero on Tuesday April 12, 2016 @02:35AM (#11477631)
Ah yeah, it went totally over my head.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by Loque on Friday April 08, 2016 @08:34AM (#11454145)
IMHO it really depends on what you are doing;

- Chatting with friends? = Whatsapp

- International drug deals? != Whatsapp

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by nxzero on Friday April 08, 2016 @08:46AM (#11454212)
Goal should be mass adoption of universal turnkey state-level OPSEC for everyday use.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by mc32 on Friday April 08, 2016 @12:53PM (#11456061)
They do this for power and legitimacy. Ranking gives them power/imprimatur and presumably would want to use this to affect and effect the direction of encryption.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by Laaw on Friday April 08, 2016 @12:29PM (#11455899)
I have absolutely zero evidence for this, but I'd bet large sums of lint from my pocket that this article was discussed by a Facebook PR person and an EFF person.

It's the kind of thing that happens all the time in the industry, but it's precisely the kind of reason I find the EFF to not be worth sending money to.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by corndoge on Friday April 08, 2016 @09:07AM (#11454348)
>runs on iPhones

Anyone but Thomas and this would be dead

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by osweiller on Friday April 08, 2016 @09:26AM (#11454461)
It's a weak strawman, though. He isn't literally saying that, but is trying to discount those who complain about closed source by comparing them to people who are apparently anti-iPhone. Then again, maybe that's exactly what you mean and you'd be right -- normally that sort of tired strawman would be dead.

It really is incredible to see tptacek discounting the closed source, completely unaudited nature of this product. A company is saying "we have total end-to-end encryption...trust us", and to believe that you trust the binary that is on your device, that it is managing keys properly (there is usually a fine line between usability and security, and usability usually wins), and you trust that they don't misuse your messages when they pass through their server. They control every aspect of the conversation, and are fully capable of completely undermining your security at any moment (if not already). In practice it's not terribly unlike the widely discredited JavaScript encryption approaches.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @11:55AM (#11455588)
What's incredible to me is that it's 2016 and people on one of the largest programming communities on the Internet are still acting like conventionally compiled iOS applications are impenetrable, but C source code for new cryptosystems is somehow instantly validated by the crowd.

It's like IDA Pro and OpenSSL never happened.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by sp332 on Friday April 08, 2016 @11:56AM (#11455601)
If you understand and verify the binary, you don't have to worry about what might happen to your messages on the company's servers.
[dead]
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by wglb on Friday April 08, 2016 @02:12PM (#11456673)
This argument has appeared throughout this discussion, yet I know of approximately zero cases (validation/comfort through disassembly) of this happen.

I am curious where you looked for these cases that you saw none.

I assure you that this happens quite regularly. And what is wrong with IDA Pro? Why would it need to advance?

This notion that security products are vetted by analyzing the binary code is absurd yet it happens on a regular basis.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by sp332 on Friday April 08, 2016 @12:32PM (#11455931)
It has been dramatically progressing, but you'd have to look around yourself to know if it's beyond what you're thinking of.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @01:24PM (#11456289)
You posted your "edit" about 20 minutes after 'sp332 correctly answered your question, and your edit is both flagrantly incorrect and rude.
[dead]
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @02:20PM (#11456731)
That wasn't a scare quote, and I don't think name-calling enhanced your argument much.
Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by maxerickson on Friday April 08, 2016 @09:38AM (#11454532)
tptacek writes a lot of pretty positive stuff about iPhone security.

It's an example of a topic people will raise to object to the EFF scorecard, not an argument being made against the iPhone.

Re:WhatsApp Rolls Out End-To-End Encryption to Its Over 1B U... by tptacek on Friday April 08, 2016 @11:03AM (#11455101)
Woosh.