News for hackers. Stuff that matters.
Re:End-to-end encryption does not prevent Facebook from acce... by jstanley on Sunday November 18, 2018 @05:18AM (#18479666)
> I mean, yeah, by that metric, Signal could too, and every other encrypted messenger.

Open source ones would be a lot less likely to get away with it.

Re:End-to-end encryption does not prevent Facebook from acce... by gcthomas on Sunday November 18, 2018 @05:30AM (#18479692)
The difference between Signal and Wattsapp is really in all the non-message-contents data that Wattsapp collects, as you can see in their privacy (hah!) policy: ( https://www.whatsapp.com/legal/#privacy-policy-information-w...)

"(We collect) hardware model, operating system information, battery level, signal strength, app version, browser information, and mobile network, connection information including phone number, mobile operator or ISP, language and time zone, and IP, device operations information, and identifiers like device identifiers (including identifiers unique to Facebook Company Products associated with the same device or account)

"...how you interact with others using our Services, and the time, frequency, and duration of your activities and interactions), log files, and diagnostic, crash, website, and performance logs and reports. This also includes information about when you registered to use our Services, the features you use like our messaging, calling, Status, or groups features, profile photo, about information, whether you are online, when you last used our Services (your "last seen"), and when you last updated your about information.

"We collect device location information if you use our location features, like when you choose to share your location with your contacts, view locations nearby or those others have shared with you, and the like, and for diagnostics and troubleshooting purposes such as if you are having trouble with our app's location features. We use various technologies to determine location, including IP, GPS, Bluetooth signals, and information about nearby Wi-Fi access points, beacons, and cell towers.

"We receive information about you from other users and businesses. For example, when other users or businesses you know use our Services, they may provide your phone number, name, and other information

"Businesses you interact with using WhatsApp provide us information about their interactions with you.

Re:End-to-end encryption does not prevent Facebook from acce... by anticensor on Sunday November 18, 2018 @05:51AM (#18479757)
> battery level, signal strength,

This reminds me Windows 10 collecting color of the device, in that it is unnecessary for operation but enough to pinpoint a person in combination.

Re:End-to-end encryption does not prevent Facebook from acce... by crtasm on Sunday November 18, 2018 @07:00AM (#18479960)
It asks you what colour your device is? Haven't run into that yet.
Re:End-to-end encryption does not prevent Facebook from acce... by anticensor on Sunday November 18, 2018 @07:12AM (#18479985)
It collects without noticing you. There is a chassis color stored in somewhere as I understand it correctly.
Re:End-to-end encryption does not prevent Facebook from acce... by MuppetMaster42 on Sunday November 18, 2018 @12:24PM (#18481444)
If you are being super paranoid...

Unless the open source app is transparently built and app store deployed from a public build server, it's very easy for the owner to inject a back-door into it.

There's no mechanism built into the app stores to validate an app against its source code.

So the owner could checkout master, add a back-door, build and publish to the app stores, and you'd update, never knowing you're exposed.

Nothing is 100% safe. It's just dependent on how much trust you assign.

Re:End-to-end encryption does not prevent Facebook from acce... by azahk on Sunday November 18, 2018 @05:33AM (#18479703)
Why?

These applications are super complex and you can't count on all eyeballs detecting a potential backdoor. And, you don't know if the code in the repo matches what you download from the App Store.

Re:End-to-end encryption does not prevent Facebook from acce... by jillesvangurp on Sunday November 18, 2018 @06:42AM (#18479910)
If your point is that it is not perfect, you are right. Case in point here is openssl which after decades of usage was so convoluted that people decided to create independent implementations to cut down on the problems that were found in it regularly.

You are also right that appstores are a problem. However, one of the nice things they do is using signatures to prevent tampering with the builds. So having a build system that produces reproducible builds and signatures means users can check whether things line up.

A bigger problem is the reliance on the phone network for identity. A lot of these chat clients insist on using telephone numbers for identifying users. This has been used to shut down chat networks in countries with telecom operators that are collaborating with governments.

If you want to stay secure, most of the chat apps out there are problematic at some level. Signal is one of the very few decent options out there. It is one of the few solutions that has both open source clients and servers and a wide community of people using it and scrutinizing it. With e.g. whatsapp, you are at the mercy of a multinational with a track record of indifference and negligence towards the goal of preserving their user's privacy and, worse, a strong incentive towards doing the exact opposite.

Re:End-to-end encryption does not prevent Facebook from acce... by gcthomas on Sunday November 18, 2018 @05:42AM (#18479732)
Signal has had its encryption code audited by researchers, and the Store binaries are signed by the developer, while the repo offers reproducable builds: you can check for yourself if the downloaded apk from Google Play matches what you built from the repo.
Re:End-to-end encryption does not prevent Facebook from acce... by xxs on Sunday November 18, 2018 @05:39AM (#18479725)
This is a very weak argument, eyeballs do find backdoors. Usually each commit is checked by few people and the introduction of the backdoor is rather obvious.

As for not knowing what has been downloading (if someone tempered with), the best approach is compiling it on your own.

Re:End-to-end encryption does not prevent Facebook from acce... by kasey_junk on Sunday November 18, 2018 @08:35AM (#18480290)
Can you cite any commits for any open source software where a back door was attempted to be introduced & code review found it pre-emptively?

The reason I ask is that this is an oft repeated claim about open source by developers yet when I talk to security people they don’t seem to care about open source nearly as much. To them inspecting binaries is table stakes anyway.

Meanwhile people write backdoors that aren’t obvious for fun. http://underhanded-c.org/

Re:End-to-end encryption does not prevent Facebook from acce... by gaius on Sunday November 18, 2018 @06:17AM (#18479836)
This is a very weak argument, eyeballs do find backdoors

Eventually, maybe. How many eyeballs and how long to find Heartbleed?

Re:End-to-end encryption does not prevent Facebook from acce... by zAy0LfpBZLC8mAC on Sunday November 18, 2018 @06:32AM (#18479876)
The question isn't whether there won't ever be backdoors, but how likely that is, how long they will stay in place undetected, and what the effects on the reputation of the product/project/committer are once they are discovered.

Bringing this up as an argument is a sensible as claiming that transparency and democracy isn't any better than a dictatorship because there is still corruption.

Re:End-to-end encryption does not prevent Facebook from acce... by Coxa on Sunday November 18, 2018 @06:27AM (#18479865)
There's a difference between a potential backdoor and a bug. While a lot of eyeballs might oversee a bug, you have to make an effort to design your backdoor to go unnoticed.
Re:End-to-end encryption does not prevent Facebook from acce... by gaius on Sunday November 18, 2018 @07:11AM (#18479983)
Good backdoors are indistinguishable from bugs, for plausible deniability