3 ms·
EFF recommending closed source clients, erm they just drop in my esteem.
by ekianjo 11y ago
EFF recommending closed source clients, erm they just drop in my esteem.
- rileymat2 11y agoThey gave it a deduction in their rating and said to prefer open source.
- evgen 11y agoOpen source does not mean your binary is secure. There are too many counter-examples of this fallacy to even bother enumerating. These widely- distributed binaries will be torn apart and inspected instruction by instruction. That is the only way we will know for sure, and you can bet people will be watching closely going forward. In this case I think lack of open source is not an issue given the reality of the distribution system.
- pdkl95 11y ago> Open source does not mean your binary is secure. Open source is necessary - not sufficient - for security. Other work has to be done. With closed binaries you can't even begin that work.
- nxzero 11y agoIs the backend for the Signal's messaging server open source? If so, they should open source the build script too.
- subliminalpanda 11y agoI believe so: https://github.com/WhisperSystems/TextSecure-Server https://github.com/WhisperSystems/TextSecure-Server
- vulpino 11y agoThey deduct points as it's still open source. And they are more applauding the fact that WhatsApp - probably the most widely used messaging app currently - has adopted strong end to end encryption, something which other clients have been loathe to do. This is a win. To disregard everything that WhatsApp and Signal have accomplished because WhatsApp isn't open source is silly.
- sickbeard 11y agoNo but to blindly trust in it is silly. Even openssl had a heart-bleed bug that persisted for years without most people realizing it. All it takes is one bug for the entire thing to be useless.
- zdkl 11y agoThe goal is not to be perfect, but to kickstart encryption adoption by a large non technical audience I believe. Sure that's no excuse for potentially bad crypto but it's worth it if this gets proper infosec into the public reach in the end. I'm confident this is a first step to having trustable encryption "in the real world" even if it's another client/company providing it later. Call me an optimist :)
- vulpino 11y agoAnd heartbleed is also than example of open source not being totally secure. It was a bug that persisted for years before it was found - and OpenSSL is open source. It's just as foolish to blindly trust OSS. There will always be holes - the main point to OSS is not to combat these, as they will exist regardless. Rather, it is so one might know exactly what they're installing/using, without having to trust the corporation behind it.
- sickbeard 11y agono it's foolish to trust something that hasn't been independently reviewed. How can EFF recommend something that hasn't even been subjected to an independent security audit?
- pdkl95 11y ago> one bug Everything can have bugs. The problem with this software is that it's a centralized single point of failure. Only a proper federated protocol can be resistant to subversion by business, government, or other interests.
- lmm 11y ago> This is a win. To disregard everything that WhatsApp and Signal have accomplished because WhatsApp isn't open source is silly. Is it? If the next Snowden uses WhatsApp on the basis of this recommendation, and it turns out (say) the NSA has backdoored their RNG and is scanning all messages sent over WhatsApp, that person is going to find themselves jailed or maybe executed. You can't say "it's secure except for not being open source"; the stakes are too high for that.
- antihero 11y agoThey explicitly stated that it was close source and Signal should be preferred,.