News for hackers. Stuff that matters.
Re:End-To-End – OpenPGP Chrome extension from Google by mentat on Wednesday June 04, 2014 @01:04AM (#7844128)
How about BEAST or CRIME?
Re:End-To-End – OpenPGP Chrome extension from Google by cornholio on Wednesday June 04, 2014 @05:53AM (#7844773)
BEAST is a design bug, insecure use of CBC mode. CRIME is a side channel attack, but the side channel that leaks information (compressed cleartext size) is not related to the language used, but again to the design of the algorithm.

The basic idea is that implementation-related side-channel attacks, such as timing and power draw, are very hard to exploit remotely. I guess you could write a JavaScript implementation of AES that is so bad that key-dependent multimillisecond jitter can be measured remotely. But it's almost impossible to do it by mistake.

The real problems of JavaScript are it's highly malleable runtime that offers no guarantees, everything is writable. So you need to improve browser support before you can write JavaScript crypto, that's why this is a great project: Google has the ability to change Chrome into a secure end-to-end platform, should they want that.

Re:End-To-End – OpenPGP Chrome extension from Google by FooBarWidget on Wednesday June 04, 2014 @09:21AM (#7845359)
Maybe power draw is hard to exploit remotely, but Remote Timing Attacks are Practical (Brumley & Boneh, Stanford, 2003): http://crypto.stanford.edu/~dabo/papers/ssl-timing.pdf