[tahoe-dev] [tahoe-lafs] #958: LAFS 301 Moved Permanently

[tahoe-lafs]

#958: LAFS 301 Moved Permanently
------------------------------------------------------------------------------------+
 Reporter:  zooko                                                                   |           Owner:            
     Type:  enhancement                                                             |          Status:  new       
 Priority:  major                                                                   |       Milestone:  eventually
Component:  code-mutable                                                            |         Version:  1.6.0     
 Keywords:  forward-compatibility backward-compatibility integrity newcaps newurls  |   Launchpad_bug:            
------------------------------------------------------------------------------------+

Comment(by davidsarah):

 Proposed CLI command:

 {{{
 tahoe permanent-redirect <olddir> <newdir>

 Redirects <olddir> permanently to <newdir>. <olddir> must refer
 to a mutable directory; <newdir> may refer to either a mutable
 or immutable directory.

 This operation can be used to revoke write access to <olddir>.
 The security of this revocation is dependent on the cooperation
 of storage servers -- an attacker would need to have the write-cap
 for <olddir> and control any K servers, in order to be able to
 write to the directory as seen by a client using that value of K.

 Backward-compatibility notes:

 All storage servers must be running Tahoe-LAFS v1.7 or later,
 otherwise this command will fail. Storage clients running a
 version before v1.7 will not automatically follow the redirection;
 they will see a shallow-frozen copy of <newdir> with an extra
 child called "redirect" (any existing "redirect" child will be
 replaced). Therefore, you should make sure that the current
 children of <newdir> reflect what you want these clients to see.
 For security, any subdirectories of <newdir> should preferably
 be immutable at the time you use "tahoe permanent-redirect".

 Clients running Tahoe-LAFS v1.7 or later will follow the
 redirection automatically and will not see any extra link.
 There is a limit on the length of a chain of redirections
 clients will follow before giving an error.
 }}}

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