4 ms·
So in a multiuser environment, the "first" client to upload an encrypted chunk and lie about it's plaintext-hash... Which would poison the well and anybody else
by Terr_ 11y ago
So in a multiuser environment, the "first" client to upload an encrypted chunk and lie about it's plaintext-hash... Which would poison the well and anybody else gets a nasty surprise when their "backup" is always corrupted.
- robryk 11y agoIf your encryption is deterministic, the second client can check with the server that Hash(Enc(chunk)) is the same on the client and server.
- signa11 11y ago> If your encryption is deterministic, the second client can check with the server that Hash(Enc(chunk)) is the same on the client and server but the chunk on the server was encrypted using a different public-key, so how can hash(pub-key-1(chunk)) == hash(pub-key-2(chunk)) ?
- Natanael_L 11y agoIsn't only the decryption keys encrypted to the public keys?
- signa11 11y ago> Isn't only the decryption keys encrypted to the public keys? from the readme, it appears (to me at least), that chunks are encrypted using public-keys. concretely, the following lines : "Every time rdedup saves a new chunk file, it's data is encrypted using public key so it can only be decrypted using the corresponding secret key. "
- robryk 11y agoThey use nacl cryptobox primitive. This means that you are right. Alas, the decryption key (they symmetric key used to encrypt this particular message) is derived deterministically from the private key and nonce. The nonce they use is the hash of the chunk. Thus, the same chunk will always be encrypted with the same symmetric key.
- mappu 11y agoMulti-user deduplication also leaks information via timing attacks (user2 can upload a million key files to see if user1 already stored one). It's better to only deduplicate on a per-user basis.