News for hackers. Stuff that matters.
Re:Megabad: A quick look at the state of Mega’s encryption by daeken on Monday January 21, 2013 @11:45AM (#5092216)
The trust model is inherently broken when doing crypto in the browser the way they are, since the code could be changed at any time. But that doesn't mean you shouldn't implement things properly outside of that.
Re:Megabad: A quick look at the state of Mega’s encryption by shin_lao on Monday January 21, 2013 @01:16PM (#5092772)
What do you mean by the code could be changed at any time.

AFAIK this applies to any software.

Re:Megabad: A quick look at the state of Mega’s encryption by daeken on Monday January 21, 2013 @01:19PM (#5092789)
Every time you visit the website, the crypto code is brand new to you. A site that securely and safely encrypted your data yesterday might be sending keys to the server tomorrow. This is a problem that's fairly unique to doing crypto on the client side in the browser.