[tahoe-dev] [tahoe-lafs] #625: Can't repair read-only dirnodes/mutable-files

[tahoe-lafs]

#625: Can't repair read-only dirnodes/mutable-files
--------------------------+-------------------------------------------------
 Reporter:  francois      |           Owner:  warner  
     Type:  defect        |          Status:  assigned
 Priority:  minor         |       Milestone:  1.6.0   
Component:  code-mutable  |         Version:  1.3.0   
 Keywords:                |   Launchpad_bug:          
--------------------------+-------------------------------------------------
Changes (by warner):

  * component:  code-dirnodes => code-mutable


Comment:

 I'm going to try to make the june release at least tolerate (i.e. skip
 over) read-only dircaps, so deep-check-and-repair can work on all the
 files.

 I've also got an idea about a relatively clean way to address this: use an
 all-zeros WE to ask the server to please validate the new share instead of
 relying upon the WE for access control. This will require significant (but
 compatible) changes to both the client and the server. Also note that the
 current mutable share format doesn't allow the server to validate the
 encrypted private key, but it can validate all the other bits. One
 criteria for the new DSA-based mutable file design (#217) is that every
 bit of the slot data must be validateable by the server (i.e. if we must
 embed key material in the share, it must be covered by the signature).

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