[tahoe-dev] [tahoe-lafs] #753: use longer storage index / cap for collision resistance

[tahoe-lafs]

#753: use longer storage index / cap for collision resistance
---------------------------+------------------------------------------------
 Reporter:  warner         |           Owner:           
     Type:  defect         |          Status:  new      
 Priority:  major          |       Milestone:  undecided
Component:  code-encoding  |         Version:  1.4.1    
 Keywords:                 |   Launchpad_bug:           
---------------------------+------------------------------------------------

Comment(by zooko):

 Wait, if you you have 4-bit storage indexes, ''and servers verify
 integrity of shares'', then you don't get an unrecoverable file, you get a
 failure to upload the second one, right?  I really like the idea of
 servers verifying the integrity of shares, because without that then even
 if you have a nice fat storage index, the first server that you upload to
 could quickly turn around and upload garbage to all the other servers,
 under the same storage index that you just told him.

 A failure to upload (backup) is a much better problem to have than a
 failure to download (recover), as long as it can be detected, understood,
 and fixed by the operators.  I.e. "Oh, we need to add servers", or "Oh, we
 need to start using longer storage indexes".  :-)

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