3 ms·
Doesn't this one seemingly trivial change (encryption) add enough annoyance for the average pirate that they'll likely use one of the bevy of competing filehost
by hkmurakami 14y ago
Doesn't this one seemingly trivial change (encryption) add enough annoyance for the average pirate that they'll likely use one of the bevy of competing filehosting sites?
Reasons I can think of using "Mega" instead of another service include (1) DL speed, (2) brand recognition, (3) less intrusive ads and less annoying capchas due to their superior financial position and scale stemming from their name recognition.
I wonder if the reasons above (or others) will be strong enough to transition Megaupload users to "Mega"
- wmf 14y agoIt sounds like their client is going to automatically perform the decryption. I would guess you'll be able to just pass in the key in the URL, so indexing sites will make Mega just as easy to use as BitTorrent is with magnet URLs. Remember that Mega only makes money if people use it.
- hkmurakami 14y agoOh I see, that would resolve my concerns then! Thank you for the insight :)
- JulianMorrison 14y agoA crypto key in the URL would ruin the deniability - their web server logs would contain the decryption keys. The whole point is to run AES in Javascript in the browser so the key never reaches them.
- mcpherrinm 14y agoLinking the key as the fragment identifier component (after a #) would prevent the server from seeing it, but still allow Javascript to have access to the key. That way you can link encrypted content with a key, and have the server not know about it. This scheme has been deployed for at least one secure pastebin.
- JulianMorrison 14y agoInteresting. I didn't know the browser keeps that part to itself.