News for hackers. Stuff that matters.
Re:MEGA is genius by oh_sigh on Sunday October 18, 2015 @11:24PM (#10410934)
Does manufactured plausible deniability provide as much protection? They could obtain all the keys used to decrypt files with a single logging statement, if they so chose.
Re:MEGA is genius by gerard on Monday October 19, 2015 @01:43AM (#10411312)
Having no cleartext to hand over in individual cases is one form of plausable deniability. Cleverly, it also appears to offer plausable deniability of your service's "primary purpose", since there are few conclusions that can be drawn from the encrypted data in aggregate. So some protection, yes, but there are certainly other ways to get yourself indicted, or your customers blocked, under such general tests.

The example in the article shows the decryption key as a URL fragment, which never hits the wire. A subpoena on Mega's own servers is one thing, but a court compelling them to collect keys from client machines? I would hope not.

Re:MEGA is genius by granos on Monday October 19, 2015 @01:55AM (#10411340)
It feels likely they could claim that any court order to transmit and log the keys would be "unduly burdensome" and would in fact fly in the face of their carefully considered business practices.
Re:MEGA is genius by DanBC on Monday October 19, 2015 @04:08AM (#10411715)
We've seen court orders that caused Hushmail to create malformed Java apps which were then silenty delivered to target machines in order to break encryption.

http://www.wired.com/2007/11/hushmail-to-war/

People pretty much have no option but to comply with court orders. Most people are not going to go to jail so that other people can continue distributing stuff.

This should be a worry with Mega and its current owners.

Re:MEGA is genius by amatix on Monday October 19, 2015 @05:10AM (#10411882)
They were talking about making offline & alternative OSS clients (via an open API) so that if they were legally forced to change the Javascript (which currently does the encryption) that it wouldn't affect the integrity of the service for those users.
Re:MEGA is genius by SixSigma on Monday October 19, 2015 @03:34AM (#10411624)
No they can't

Notice the format of the URL

example.com/fileA#encryption-key

All MEGA has logged is: example.com/fileA

encryption-key

is generated client side and only sent to recipients, not the provider.

Re:MEGA is genius by oh_sigh on Monday October 19, 2015 @04:35PM (#10415531)
That's why I said one logging statement could grab the key. Just log the fragment to a service that you run somewhere, and all of the sudden you have the key.
Re:MEGA is genius by SixSigma on Tuesday October 20, 2015 @03:04AM (#10417832)
who is "you"?

The fragment is only ever transmitted by the uploaded to the recipient. I'm not familiar with Mega but presumably this transmission is also encrypted.

So your chance of getting it is low.

And certainly Mega can deny ever receiving it.

Re:MEGA is genius by oh_sigh on Tuesday October 20, 2015 @12:59PM (#10420341)
"You" being the people who wrote the client side script. Yes, the fragment is not normally transmitted to the server, but since the user is running code on their browser which was provided to them by mega, all mega needs to do is log the fragment back to their servers with a simple ajax call.

The point wasn't that mega can deny ever getting the key - the point was that this "security" system in place is very obviously designed to workaround the problem of mega knowing what files they were trading. This would probably be viewed as willful blindness and not actually protect them in court:

see: https://news.ycombinator.com/item?id=10415535

Re:MEGA is genius by AgentME on Monday October 19, 2015 @12:05AM (#10411053)
Not if the site used the service worker feature to pin secure versions of the site javascript on first connection.
Re:MEGA is genius by Tepix on Monday October 19, 2015 @04:41AM (#10411803)
Got a good guide for that?
Re:MEGA is genius by girvo on Monday October 19, 2015 @08:20AM (#10412397)
From when I looked last, it's super experimental and not quite there yet.

This link[0] explained it reasonably well to me, though I'm still not sure on the security implications of pinning JS through it.

[0] https://github.com/slightlyoff/ServiceWorker/blob/master/exp...

Re:MEGA is genius by gojomo on Monday October 19, 2015 @04:11AM (#10411725)
Courts may not look kindly on such 'willful blindness':

https://en.m.wikipedia.org/wiki/Willful_blindness

Re:MEGA is genius by oh_sigh on Monday October 19, 2015 @04:36PM (#10415535)
This seems pretty relevant from your link:

> A famous example of such a defense being denied occurred in In re Aimster Copyright Litigation, 334 F.3d 643 (7th Cir. 2003), in which the defendants argued that the file-swapping technology was designed in such a way that they had no way of monitoring the content of swapped files. They suggested that their inability to monitor the activities of users meant that they could not be contributing to copyright infringement by the users. The court held that this was willful blindness on the defendant's part and would not constitute a defense to a claim of contributory infringement.

Re:MEGA is genius by Tepix on Monday October 19, 2015 @04:42AM (#10411807)
They could easily grab the key with a little bit of JavaScript, however it would be detectable on the client side.