[tahoe-dev] [tahoe-lafs] #954: revoke write authority

tahoe-lafs trac at allmydata.org
Mon Feb 15 05:20:59 UTC 2010


#954: revoke write authority
-------------------------------------------------------------+--------------
 Reporter:  zooko                                            |           Owner:           
     Type:  defect                                           |          Status:  new      
 Priority:  major                                            |       Milestone:  undecided
Component:  code-mutable                                     |         Version:  1.6.0    
 Keywords:  integrity capleak forward-compatibility newcaps  |   Launchpad_bug:           
-------------------------------------------------------------+--------------
 As described in http://allmydata.org/pipermail/tahoe-
 dev/2009-June/001995.html , the easiest kind of revocation to implement in
 a distributed, robust way is also the kind of revocation that I most
 urgently need: revoke the write-authority embodied in a specific cap.

 The way to implement this is to define a special out-of-band symbol (i.e.,
 something unambiguously distinct from file contents) which means "this
 file has been petrified". That would be a way to take a mutable file and
 turn it into a petrified file (formerly mutable but now immutable).

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


More information about the tahoe-dev mailing list