News for hackers. Stuff that matters.
Re:Facebook Messenger begins testing end-to-end encryption u... by pilif on Friday July 08, 2016 @10:46AM (#12055903)
Yes. But let's assume FB doesn't want the keys (because if they have them, then it's no longer E2E encryption), then client-side generated keys in a browser are still exposed to XSS attacks and extensions.

Installing a malicious extension, tricking users into typing commands in the developer tools, XSSing FB, all of these are much easier to do than attacking a native app on a phone.

Re:Facebook Messenger begins testing end-to-end encryption u... by aianus on Friday July 08, 2016 @12:24PM (#12056679)
How is the possibility of XSS worse than the status quo (plaintext)? Thats like saying SSL is useless on desktop because root kits and keyloggers exist on desktop.
Re:Facebook Messenger begins testing end-to-end encryption u... by WorldMaker on Friday July 08, 2016 @01:12PM (#12057061)
A false sense of security can be more damaging than no sense of security.

Certainly it can be important to know when you have a "no compromises" security option versus "mostly better than plaintext but maybe not secure".

It could be a UX judgment to not confuse users they have a "secure connection" when in fact they might not. Look at all the various attempts over the years browsers have made to keep the UX semi-reliable and easy for users to understand whether or not their SSL connection is secure.