Re:Megabad: A quick look at the state of Mega’s encryption
by loeg on Monday January 21, 2013 @11:53AM
(#5092259)
But both clients still need to be able to decrypt it with their separate keys... even if the cleartext hash matches, the stored data is ciphertext and can only be encrypted with one user's key.
[ Parent
| on HN ]
Re:Megabad: A quick look at the state of Mega’s encryption
by B-Con on Monday January 21, 2013 @12:20PM
(#5092419)
It's possible: http://crypto.stackexchange.com/questions/729/is-convergent-... .
The trick lies in ensuring the key used for encryption is linked to the file, not the user. You then have to store a separate key for each encrypted file (and that encryption key is probably going to need to be wrapped by your actual user key for storage).
Re:Megabad: A quick look at the state of Mega’s encryption
by loeg on Monday January 28, 2013 @10:43PM
(#5132199)
But, how does the second user to upload the same file know the file's encryption key (since presumably the server only knows ENCRYPT(FILE_KEY with USER1_KEY))?
It seems like either the server must know the file's encryption key, or the key must be derivable from the contents... which is no good.