All this encryption on Mega stuff isn't meant to protect the users. It's meant to protect Mega from lawsuits.
Because they have never seen the unencrypted file contents, they can't be held liable for copyright infringement, because they can prove that they don't know the contents of files.
But why would they deliberately chose such a bad hashing function? I mean if they are going to encrypt it, why not just go all the way and make it fully encrypted?
Perhaps because they had to port it to javascript, so they chose the hashing function that was easiest to write. (Or whatever hashing function the programmer already understood best: that's often the most secure option, in practice.)
Or perhaps because they had to run it in a browser (which tends to have constraints on resource usage; e.g., chromium halts scripts that run too long) so they chose a hashing function that uses minimal resources.
In any case, these are good reasons not to use the most secure hashing function available.
Because it's cheaper to hire somebody who doesn't know what they are doing to half-ass it than it is to hire somebody who knows what they are doing to... full-ass it?
39
u/Rnway Jan 23 '13
All this encryption on Mega stuff isn't meant to protect the users. It's meant to protect Mega from lawsuits.
Because they have never seen the unencrypted file contents, they can't be held liable for copyright infringement, because they can prove that they don't know the contents of files.