thought about chunk key hashing
This commit is contained in:
parent
014794f4ed
commit
1755c5de40
1 changed files with 9 additions and 0 deletions
|
@ -209,3 +209,12 @@ cannot check exact file sizes.
|
||||||
|
|
||||||
If padding is enabled, gpg compression should be disabled, to not leak
|
If padding is enabled, gpg compression should be disabled, to not leak
|
||||||
clues about how well the files compress and so what kind of file it is.
|
clues about how well the files compress and so what kind of file it is.
|
||||||
|
|
||||||
|
## chunk key hashing
|
||||||
|
|
||||||
|
A chunk key should hash into the same directory structure as its parent
|
||||||
|
key. This will avoid lots of extra hash directories when using chunking
|
||||||
|
with non-encrypted keys.
|
||||||
|
|
||||||
|
Won't happen when the key is encrypted, but that is good; hashing to the
|
||||||
|
same bucket then would allow statistical correlation.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue