

Telegram has been under fire from the start, lol. 'we have math PhDs" 🤷
Cryptography nerd
Fediverse accounts;
[email protected] (main)
[email protected]
[email protected]
Bluesky: natanael.bsky.social
Telegram has been under fire from the start, lol. 'we have math PhDs" 🤷
There’s also a big difference between published specifications and threat models for the encryption which professionals can investigate in the code delivered to users, versus no published security information at all with pure reverse engineering as the only option
Apple at least has public specifications. Experts can dig into it and compare against the specs, which is far easier than digging into that kind of code blindly. The spec describes what it does when and why, so you don’t have to figure that out through reverse engineering, instead you can focus on looking for discrepancies
Proper open source with deterministic builds would be even better, but we aren’t getting that out of Apple. Specs is the next best thing.
BTW, plugging our cryptography community: [email protected]
Looks like the same dev from reddit
https://www.reddit.com/r/crypto/comments/1iumxl3/how_far_can_i_push_closesource_code_towards_being/
No audits and doesn’t want to share the code
https://www.reddit.com/r/crypto/comments/1iumxl3/how_far_can_i_push_closesource_code_towards_being/
Wireguard is most reliable in terms of security. For censorship resistance, it’s all about tunneling it in a way that looks indistinguishable from normal traffic
Domain or IP doesn’t make much of a difference. If somebody can block one they can block the other. The trick is not getting flagged. Domain does make it easier to administer though with stuff like dyndns, but then you also need to make sure eSNI is available (especially if it’s on hosting) and that you’re using encrypted DNS lookups