From bfafd557d3b6a14d358b0d25a12b7656df3db983 Mon Sep 17 00:00:00 2001 From: davidsarah <> Date: Sun, 11 Oct 2009 03:39:35 +0000 Subject: [PATCH] move URL relevant to footnote 2 [Imported from Trac: page NewCaps/WhatCouldGoWrong, version 26] --- NewCaps/WhatCouldGoWrong.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/NewCaps/WhatCouldGoWrong.md b/NewCaps/WhatCouldGoWrong.md index f4127b1..e7bd88f 100644 --- a/NewCaps/WhatCouldGoWrong.md +++ b/NewCaps/WhatCouldGoWrong.md @@ -21,7 +21,7 @@ where *k* = bitlength(*K1*), *n* = bitlength(*R*), *s* = bitlength(*S*), *t* = b 1. *shape-shifter immutable file*: creator creates more than one file matching the immutable file readcap -2. *roadblock*: attacker prevents uploader (including repairer) from being able to write a real share into the right storage index; *speedbump*: attacker adds his bogus share into the list of shares stored under the storage index by the same method; downloader has to download, examine, and discard the bogus (*K1enc*,*Dhash*,*V*)'s until it finds the real one +2. *roadblock*: attacker prevents uploader (including repairer) from being able to write a real share into the right storage index; *speedbump*: attacker adds his bogus share into the list of shares stored under the storage index by the same method; downloader has to download, examine, and discard the bogus (*K1enc*,*Dhash*,*V*)'s until it finds the real one. Also see 3. *undeletion*: attacker makes a deleted file (for which it need not have had a read cap) accessible at its previous storage index, and readable by previous read caps @@ -30,6 +30,3 @@ where *k* = bitlength(*K1*), *n* = bitlength(*R*), *s* = bitlength(*S*), *t* = b 5. Brute force costs assume a single-target attack that is expected to succeed with high probability. Costs will be lower for attacking multiple targets or for a lower success probability. (Should we give explicit formulae for this?) 6. *roadblock*/*speedbump* attacks could be restricted to holders of a read cap by use of an extra signature, as in the Elk Point 3 design (diagram at for mutable files). - - - \ No newline at end of file