>Telegram doesn't have reproducible builds, do they? So if they really wanted to fuck people over, all they had to do is to ship a build that uses predictable P

>Telegram doesn't have reproducible builds, do they? So if they really wanted to fuck people over, all they had to do is to ship a build that uses predictable PRNG. This doesn't really matter that much, the source code isn't very helpful while auditing a RNG. Most of the time Telegram doesn't even encrypt conversations, yet this is their main selling point. >So, yes, I think that you are seeing things that are not there and it's yet another case of stupidity rather than malice on part of Telegram's devs. No. I just don't think it matters whether this was stupidity or malice, sufficiently advanced stupidity is indistinguishable from malice. This was not your typical crypto fail. You suggested that this is a common kind of error, can you point at someone else that did this? I think it's fair to assume malice in the case of Telegram, their "secure encrypted messaging" application still doesn't even encrypt most conversations.