3 ms·
> To participate in some parts of society WhatsApp is now a de facto requirement. A whole nation blindly agrees to whatever terms of use Facebook drafts. Same
by Fnoord 8y ago
> To participate in some parts of society WhatsApp is now a de facto requirement. A whole nation blindly agrees to whatever terms of use Facebook drafts.
Same if you don't have a Facebook account. Speaking of which, WhatsApp was the defacto IM standard before it was bought by Facebook. Previously it was MSN Messenger (or whatever it is called these days. Skype?) and that was horrible as well. XMMP was at least federated, and had backwards compatibility.
The advantage WhatsApp has over MSN is that the data is E2EE.
There are some people who push for an alternative called Telegram, which uses home brew cryptography instead of established standards.
Though if I look at the Mastodon drama (recently posted on HN, apparently from 2017) federated in practice can lead to fractured communities. Heck, you can even see that in the history of IRC (how EFnet and IRCnet got started).
- ReverseCold 8y ago> There are some people who push for an alternative called Telegram, which uses home brew cryptography instead of established standards. No, it might as well have no end-end cryptography. The crypto is only enabled for "Secret Chats" and Calls, and I have never seen anyone actually use the secret chat functionality. Using a secret chat limits you to one device and blocks features like bots, so most people don't want to use it.
- reitanqild 8y ago>> There are some people who push for an alternative called Telegram, which uses home brew cryptography instead of established standards. > No, it might as well have no end-end cryptography. Parent says cryptography, not end-to-end cryptography. Cryptography provides value even if it is not end-to-end (it limits the attack surface). There's a lot to say about Telegram, but can please stick to the facts?
- arkadiytehgraet 8y agoHave you actually seen the implementation of the WhatsApp clients on iOS / Android? How can you say that the data is E2EE when there are no sources, no verifiable builds, nothing but just statements that "yes, we do use E2EE"? On the contrary, you have open protocol with verifiable implementation and available sources of the Telegram client for mobile platforms; yet you automatically disregard it just because it is not developed by Moxie or whatever. I am still baffled how people completely turn off their critical thinking when it comes to encryption; I guess this is a fine example how marketing actually works well.
- Fnoord 8y agoYes, WhatsApp is proprietary software and you did describe some issues. However, the context of the discussion is finding a WhatsApp alternative and rolling it out; Telegram is not a viable alternative. The point never was we should stick to WhatsApp. If the standards Telegram opted not to use are broken we can all be easily hacked. So avoiding those standards just for the sake of using your own, is snake oil. Thinking you know better than the consensus of the whole security community is, in this case, unnecessarily arrogant and harmful. [EDIT]I'll edit my post since I can't reply: WhatsApp has E2EE, but you cannot verify the source. Telegram uses home brew crypto. Stop distracting the reader from that, you scum. As for the issues with Telegram it isn't "one" security researcher. I found 2 in 30 seconds: Matthew Green and Micah Lee [1] [2] [1] https://medium.com/@thegrugq/operational-telegram-cbbaadb9013a https://medium.com/@thegrugq/operational-telegram-cbbaadb901... [2] https://www.schneier.com/blog/archives/2016/06/comparing_messa.html https://www.schneier.com/blog/archives/2016/06/comparing_mes... [/EDIT]
- arkadiytehgraet 8y agoThe only context in the post I replied was about WhatsApp being E2EE, which is factually wrong and incorrect, and we should not propogate this misbelief any further than it already is. I mean, this is literally the quote from the post: >The advantage WhatsApp has over MSN is that the data is E2EE. Where in my post have I mentioned that Telegram uses their own crypto just for the sake of using their own? I'll save you some time: I did not mention it at all. Why did you then even bother to say anything about "snake oil" and "considered harmful"? Moreover, if security community (for some reason always represented by 1 person) says that unverifiable, closed-source solution is secure just because they said so, then I'll be better off without trusting them, and the actual common sense tells me to stay away as far as I can from anything they do.
- Canada 8y agoYes, and Telegram being open allows us to confirm with absolute certainty that it uses no E2EE by default. We don't have the WhatsApp source code, but we don't have to do a lot of reverse engineering to see that it uses this: https://github.com/signalapp/libsignal-protocol-c https://github.com/signalapp/libsignal-protocol-c But yeah, you're right, it could be sending plaintext or deliberately leaking keys somewhere. Unless someone really reverses it we won't know it doesn't as surely as we know that Telegram doesn't use encryption at all.