jgaunt/duplicacy
1
0
Fork 0
mirror of https://github.com/gilbertchen/duplicacy synced 2026-01-06 10:34:04 +00:00
Code Issues Releases Wiki Activity

Wiki was moved to forum.duplicacy.com

TheBestPessimist
2018-09-11 08:14:48 +02:00
parent f4e8f84223
commit 957e002c32
1 changed files with 2 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
Encryption.md

@@ -1,18 +1,3 @@
When encryption is enabled (by the -e option with the *init* or *add* command), Duplicacy will generate 4 random 256 bit keys:
The wiki has moved to a new home on the [Duplicacy Forum](https://forum.duplicacy.com).
* *Hash Key*: for generating a chunk hash from the content of a chunk
* *ID Key*: for generating a chunk id from a chunk hash
* *Chunk Key*: for encrypting chunk files
* *File Key*: for encrypting non-chunk files such as snapshot files.
Here is a diagram showing how these keys are used:
[[https://github.com/gilbertchen/duplicacy-beta/blob/master/images/duplicacy_encryption.png|alt="encryption"]]
Chunk hashes are used internally and stored in the snapshot file. They are never exposed unless the snapshot file is decrypted. Chunk ids are used as the file names for the chunks and therefore exposed. When the *cat* command is used to print out a snapshot file, the chunk hashes stored in the snapshot file will be converted into chunk ids first which are then displayed instead.
Chunk content is encrypted by AES-GCM, with an encryption key that is the HMAC-SHA256 of the chunk Hash with the *Chunk Key* as the secret key.
The snapshot is encrypted by AES-GCM too, using an encrypt key that is the HMAC-SHA256 of the file path with the *File Key* as the secret key.
These four random keys are saved in a file named 'config' in the storage, encrypted with a master key derived from the PBKDF2 function on the storage password chosen by the user.
Your page is available at: https://forum.duplicacy.com/t/encryption-of-the-storage/1085