Earlier quoted context omitted.
Wouldn't this allow MEGA to also get a copy of the key so they can decrypt your data?
Only if they had a copy of the original plaintext file.
Mega has launched
101–110 of 272 posts
Re: Mega has launched
#102I 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…
The user's javascript that encrypted the file can also make a hash send it to mega, and then they check if they already have that. EDIT: They never get to see your key or what is in the file.
Re: Mega has launched
#103Does 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…
| Each user account uses a symmetric master key to ECB- | encrypt all keys of the nodes it keeps in its own trees. | This master key is stored on MEGA's servers, encrypted | with a hash derived from the user's login password. The key is stored encrypted on their servers, but is unlocked with your password. Technically they could capture your password and unlock the key, gaining access to the files.
Unlocking a key requires a real password but the server knows only the hashed version. This way they can't capture the real password to unlock. The trick would be to make sure server always gets only the hashed password. Even at website login, the password must be hashed before sending!
We used similar crypto for http://timegt.com product where everything is end-to-end encrypted with a keypair generated by the user yet stored at the server. But it's stored at the server in a locked form that can be opened with a password that user entered. But this password is never sent to the server, only the password hash is and is used only to make sure that it's ok to send this locked key to the user. Hopefully this didn't sound too confusing now...
Re: Mega has launched
#104"Warning: You are using an outdated browser, which adversely affects your file transfer performance. Please upgrade to Google Chrome." is this a joke? I'm on FF19
Further, the site looks very much polished in Chrome and its hard to find anything to blame for. If they did benchmark testing and realized Chrome works the best for decryption/encrypting/etc, I don't blame them for giving up on other browsers.
Re: Mega has launched
#105It's just hard for me to respect the man, because he's not fighting for information freedom, he's fighting for as much cash, status, and power as he can get his hands on.
Re: Mega has launched
#106Earlier quoted context omitted.
"A node token ("magic cookie") grants access to a subtree of the issuing user's filesystem. An associated symmetric key is required to decrypt and/or store decryptable data." https://mega.co.nz/#developers Apparently, they use unsalted symmetric key encryption which allows them to discover [hash(file), password] duplicates. By comparison, the old Megaupload would apparently deduplicate based on [hash(file)] matches.…
I'm not entirely sure what they mean by a "magic cookie" here. The document does say it uses public/private keys for data transfer. You would not usually use public/private for data storage because of the huge keysizes required.
If they use asymmetric encryption for data transfer, then how does that work as part of a convergent encryption scheme? Wouldn't all of the file hashes be different at that point?
Re: Mega has launched
#107Earlier 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.
Re: Mega has launched
#108I see Kim Dotcom as a stereotypical gangster who makes money by delivering illegal products. He has the narcissistic personality and lifestyle trappings to go with it. He even wants to buy protection from New Zealand itself by bringing free fibre optic cable to the island! It's just hard for me to respect the man, because he's not fighting for information freedom, he's fighting for as much cash, status, and power as…
Re: Mega has launched
#109Earlier quoted context omitted.
Possibly convergent encryption, basically when you encrypt the file you use a hash of the file as the key. This key can then be encrypted with several different passwords meaning that several people can decrypt this file.
This? http://crypto.stackexchange.com/questions/729/is-convergent-... http://www.ssrc.ucsc.edu/Papers/storer-storagess08.pdf It seems really interesting, so they can check for duplicates while keeping files secure. Thanks!
"However, one more attack: an attacker can guess plaintexts and test if you have that file."
If that's the case, pirates beware.
Re: Mega has launched
#110The clean interface makes the tagline (lifted from Daft Punk w/o credit) that much more conspicuous. Clearly, some things haven't changed.