@anony_root @Telegram My reading was that no, the issues are fundamental to T building their own crypto algorithm (why?). Not fixed.
-
-
Replying to @onetruecathal
@onetruecathal@anony_root The issue was fixed, of course. See https://telegram.org/blog/crowdsourcing-a-more-secure-future … also: https://core.telegram.org/techfaq1 reply 2 retweets 1 like -
Replying to @telegram
@telegram@anony_root That in no way addresses any of the substantial risks of your poorly designed custom algorithm.1 reply 0 retweets 0 likes -
Replying to @onetruecathal
@onetruecathal@anony_root We welcome (and reward) any comments on actual vulnerabilities that could be identified. security@telegram.org8 replies 2 retweets 1 like -
Replying to @telegram
@telegram@anony_root And as@whispersystems are practically *shoving* security-conscious users away by insisting on Google Play, you win.2 replies 0 retweets 0 likes
@onetruecathal There were 0.6 TextSecure GitHub notifications per minute from 1am to 9am. Anything you can do to help is appreciated.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.