41–50 of 272 posts
A lot of people say that megaupload is back, but if I'm not wrong this is totally something different then megaupload or do I make a mistake? You can't share a link with the public anymore, only with an emailadres.
http://gizmodo.com/5977265/how-megas-encryption-will-protect...
which makes it no different to before, except this time they're hoping deniability is better than openly facilating piracy in their internal communications.
Earlier quoted context omitted.
Well, why do you use Safari?
I use Safari because in my experience Chrome is rather buggy on a Mac. Particularly with regard to Spaces. E.g., if I move a Chrome window to a different Space, all of my other Chrome windows will tag along for the ride. It makes using Chrome rather unbearable. Additionally, Safari's interface for managing bookmarks is much nicer.
So, it generated a key... which is being stored where? I can't seem to download it?
If you could download it, what use would it have. ;)
However, that's not how Mega works. They're still storing a symmetric key on their server. They're just encrypting before storing for deniability reasons. https://mega.co.nz/#developers
My first upload: https://mega.co.nz/#!jFlzGQiZ!CL2dMi5IAYLUp3ZQ5JS7nmW0sYtudf...
After signing up, MEGA suggested that I download Google Chrome to use the service (I was using Safari). I was expecting some affiliate link there, but there wasn't any.
Well, why do you use Safari?
8. Our service may automatically delete a piece of data you upload or give someone else access to where it determines that that data is an exact duplicate of original data already on our service. In that case, you will access that original data.
Duplicate check, I get that. But, how do they do it? They say the files are encrypted on the browser, so if I upload file X and other user uploads X too, they can't know they're the same because both uploads are encrypted. So, they can check only for duplicates of the encrypted outcome of each file. But, wouldn't that be inefficient? Probability of collision in encrypted files is (AFAIK) really low, something like 2^(-N), N being the size of the file on bits... If I did it well, it'd be a collision probability of 7.458E-155 for a file of 1MB.
EDIT: Added example.
Does anyone understand how their implementation of client-side encryption is actually supposed to make my data safer? After logging in for the first time, a 2048-bit RSA key pair was generated, but it seems that every time I log in I just use a username (email) and password. Does that mean the RSA private key is stored on MEGA's servers? If so, doesn't that render the whole "client side encryption" bit moot? If MEGA…
[1] https://mega.co.nz/#help_security
EDIT: The senario in the posts above sound more likely. The exact text of the help is "No usable encryption keys ever leave the client computers (with the exception of RSA public keys)." So they probably store an encrypted version of the keys server side.
I just found a weird things on they ToS [1] ... 8. Our service may automatically delete a piece of data you upload or give someone else access to where it determines that that data is an exact duplicate of original data already on our service. In that case, you will access that original data. Duplicate check, I get that. But, how do they do it? They say the files are encrypted on the browser, so if I upload file X an…
