summaryrefslogtreecommitdiff
path: root/doc/design/assistant
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-07-25 15:12:51 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-07-25 15:12:51 -0400
commitacbd521c0e7fd7176775378845ff8f4f65bf20c0 (patch)
tree61e9b2d840d3e35e50b3a5f1b6fa8dfcf1493335 /doc/design/assistant
parent956807053d627355157f1df51667b2a61f57ab60 (diff)
thought about chunk key hashing
Diffstat (limited to 'doc/design/assistant')
-rw-r--r--doc/design/assistant/chunks.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/design/assistant/chunks.mdwn b/doc/design/assistant/chunks.mdwn
index d7517243c..b5a86ef82 100644
--- a/doc/design/assistant/chunks.mdwn
+++ b/doc/design/assistant/chunks.mdwn
@@ -209,3 +209,12 @@ cannot check exact file sizes.
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.
+
+## 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.