Changes between Version 25 and Version 26 of NewCaps/WhatCouldGoWrong

Timestamp:

2009-10-11T03:39:35Z (15 years ago)

Author:

davidsarah

Comment:

move URL relevant to footnote 2

NewCaps/WhatCouldGoWrong

@@ -20 +20 @@
 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 http://allmydata.org/pipermail/tahoe-dev/2009-October/002959.html
 
 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
@@ -29 +29 @@
 
 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 http://jacaranda.org/tahoe/mutable-addonly-elkpoint-3.svg for mutable files).
-
-
-http://allmydata.org/pipermail/tahoe-dev/2009-October/002959.html