formatting
[Imported from Trac: page NewCaps/WhatCouldGoWrong, version 9]
parent
d5eb2978e0
commit
7697b98dd5
|
@ -19,7 +19,9 @@ This is about What Could Go Wrong with the "Elk Point 2" immutable file caps: <h
|
|||
where *k* = bitlength(*K1*), *n* = bitlength(*R*), *t* = bitlength(*T*), *u* = bitlength(*U*), *d* = bitlength(*KD*).
|
||||
|
||||
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
|
||||
|
||||
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
|
||||
|
||||
<http://allmydata.org/pipermail/tahoe-dev/2009-October/002959.html>
|
Loading…
Reference in a new issue