3 ms·
In this case "private" have nothing to do with the code license. Problem with Telegram is that protocol and cryptography they use is their own. They might use b
by SXX 9y ago
In this case "private" have nothing to do with the code license. Problem with Telegram is that protocol and cryptography they use is their own. They might use better reviewed protocol like one of Signal, but they didn't.
No need to explain what dangers same strategy going to cause with cryptocurrencies.
- unicornporn 9y agoWas the Signal protocol reviewed in 2013 when Telegram was launched? It seems it was developed in 2013. I'd say the biggest problem with Telegram is the fact that E2EE isn't enabled by default and no one (that I've chatted with) uses it.
- def_true_false 9y agoThe official desktop client doesn't even support it, after years of people asking for it. Telegram is basically equivalent to Hangouts or any other random chat app, if you care about security.
- unicornporn 9y agoYup, terrible. The native macOS desktop client (available in App Store) actually supports it. At least it did when I tried it.
- dfox 9y agoPeople will tell you, that there is big gaping crypto vulnerability in Telegrams client-server crypto because it is not secure under CCA. In fact this is only certificational weakness (ie. attacker can replace message with different ciphertext that encodes exactly same message). The crypto is somewhat weird, but it is clear that motivation for the weirdness is getting small ciphertexts.