[tahoe-dev] [tahoe-lafs] #654: make the storage index be the verifier cap

[tahoe-lafs]

#654: make the storage index be the verifier cap
---------------------------+------------------------------------------------
 Reporter:  zooko          |           Owner:           
     Type:  enhancement    |          Status:  new      
 Priority:  major          |       Milestone:  undecided
Component:  code-encoding  |         Version:  1.3.0    
 Keywords:                 |   Launchpad_bug:           
---------------------------+------------------------------------------------

Comment(by warner):

 note that the peer-selection-index table offers some games to an attacker:
 they could upload a share for file A and pretend that it has the peer-
 selection-index for file B, with the goal to disrupt someone who is trying
 to upload file B (and are incorrectly told that the server already has a
 share for that file, which requires downloading the entire share to
 verify). I suspect that this is not a very large problem, though.

 Also, we might want new server-side share file format, to record the peer-
 selection-index on the bucket label (the same place that holds the
 leases). This would be used to rebuild the table from the sharefiles,
 since we consider the sharefiles to be canonical and all other tables to
 be caches or performance-improving indices. The peer-selection-index would
 not be verified like the rest of the share (making it even more
 appropriate to put on the outside of the container rather than the
 inside).

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/654#comment:2>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid