-
@matthew_d_green @moxie The real problem with this was not storing metadata on the server, encrypted with a poor-entropy PIN and some SGX-handwavy server side mitigation (which indeed is better than most other messengers). The problem is the modal dialog and not giving an option when starting the app.On twitter.com
♻️ 1 Retweets ❤️ 9 Favorites Mood -2 🙁
-
@matthew_d_green @moxie I was personally stumped - I had to quickly get at a message received a week ago to allow my kid to enter an important video conference. At that point I was totally unprepared to think about the implications, come up with a good PIN, and write it down. I just wanted the message.Permalink On twitter.com
-
@matthew_d_green @moxie That UX choice is such an anti-pattern that it was hard to believe @signalapp would do it that way, and I spent 2 minutes trying to figure out what I was missing and how I could skip the dialog / disable the option. But no, to get your old messages, you have to enter a PIN. Now.Permalink On twitter.com
-
@matthew_d_green @moxie @signalapp I could speculate which PINs the 99% that @moxie refers to will choose when given no choice. I could speculate which of their other PINs these will match, creating additional threat vectors when (not if) the SGX mitigation breaks. Android lockscreens have been there. So I won't.Permalink On twitter.com