summaryrefslogtreecommitdiffhomepage
path: root/doc/todo/delay_some_uploads_to_prevent_correlation.mdwn
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2017-08-16 11:41:25 -0700
committerSean Whitton <spwhitton@spwhitton.name>2017-08-16 11:41:25 -0700
commit379f036b39e0f7dac360ba04b281f6ea4ce8f20e (patch)
tree01a86517d6234562088561c3c4b51365ed722807 /doc/todo/delay_some_uploads_to_prevent_correlation.mdwn
parent680449e656820db2b899a8631060cf62359b9b74 (diff)
parent0229f026b1ae0344c4c052593564800035268d81 (diff)
downloadkeysafe-379f036b39e0f7dac360ba04b281f6ea4ce8f20e.tar.gz
Merge tag '0.20170811'
tagging package keysafe version 0.20170811 # gpg: Signature made Fri 11 Aug 2017 03:58:54 PM MST # gpg: using RSA key 28A500C35207EAB72F6C0F25DB12DB0FF05F8F38 # gpg: Good signature from "Joey Hess <joeyh@joeyh.name>" [full] # Primary key fingerprint: E85A 5F63 B31D 24C1 EBF0 D81C C910 D922 2512 E3C7 # Subkey fingerprint: 28A5 00C3 5207 EAB7 2F6C 0F25 DB12 DB0F F05F 8F38
Diffstat (limited to 'doc/todo/delay_some_uploads_to_prevent_correlation.mdwn')
-rw-r--r--doc/todo/delay_some_uploads_to_prevent_correlation.mdwn19
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/todo/delay_some_uploads_to_prevent_correlation.mdwn b/doc/todo/delay_some_uploads_to_prevent_correlation.mdwn
new file mode 100644
index 0000000..5b9e324
--- /dev/null
+++ b/doc/todo/delay_some_uploads_to_prevent_correlation.mdwn
@@ -0,0 +1,19 @@
+In backup, only upload to some servers immediately, and delay the rest
+for up to several days, with some uploads of chaff, to prevent
+collaborating evil servers from correlating related shards.
+
+How many servers should be uploaded to immediately? The safe answer is at least
+M (--neededshares); that way the secret key does get backed up immediately.
+
+Uploading to less would be more secure, but risks the user thinking it
+finished backing up the key, and eg, wiping their laptop. So careful
+messaging would be needed in this case.
+
+Might just upload M-1 shares immediatly, and show a dialog saying, the
+backup will be completed next Wednesday, or click here to finish it now.
+
+----
+
+Also, when there are multiple chunks, they are currently uploaded in order.
+That could easily be shuffled, with server A getting its share of chunk 2
+first, server B its share of chunk 3 first, etc.