Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you use group chats or unencrypted individual chats, then it's absolutely not secure. I don't use those for the security though. It's just a really nice messenger that's not Messenger. But it does also have E2E encrypted chats, and that's what you should use if you're trying to keep your conversation secret. Unfortunately many people aren't aware of that, and just assume Telegram is secure by default.


Even Telegram's encrypted chats have not had nearly enough analysis to be trusted. They used to use some bad home-grown techniques, now it's just "probably secure enough".

Their client code also isn't really open source, even though they claim it is. While Signal has reproducible builds.


Huh? Their client code isn't just fully open-source, it also has reproducible builds both on Android and iOS, has been for a while. Doesn't Signal only have them on Android? It's a great app either way but if RBs matter, that's a little knock against it.


Where did you get that idea from?

Their client code is not usable because they don't provide working instructions for compiling it. If you can't compile it, they can't have reproducible builds.

For example, see this issue from 2019 which the developers still haven't replied to:

https://github.com/TelegramMessenger/Telegram-iOS/issues/97

There are a lot more issues about people not being able to use the code, none of which get any replies from the owners.


GitHub builds directly from their source code just fine: https://github.com/TelegramMessenger/Telegram-iOS/actions/ru...

(uses this script: https://github.com/TelegramMessenger/Telegram-iOS/blob/maste...)

And here are few recent examples of them helping people to solve build issues: https://github.com/TelegramMessenger/Telegram-iOS/issues/968... https://github.com/TelegramMessenger/Telegram-iOS/issues/986... https://github.com/TelegramMessenger/Telegram-iOS/issues/992...

How were you digging to find an irrelevant issue yet omitted all of this? I really don't see the picture you're trying to paint.


It certainly is usable. I'd used Telegram FOSS from F-Droid for quite long before switching to Nekogram (also on F-Droid), a third-party Telegram client with some extra features.

Incidentally, Signal is still not available on F-Droid, and Signal developers are known to be hostile towards third-party clients (for "security reasons." Almost like I've heard that argument before from a certain smartphone manufacturer...)


Yep, I also use Nekogram. I like how open the client aspect is of Telegram.


From their official announcement of reproducible builds. And this seems to be the instructions: https://core.telegram.org/reproducible-builds




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: