Changes between Initial Version and Version 9 of Ticket #954


Ignore:
Timestamp:
2013-12-27T23:48:03Z (11 years ago)
Author:
zooko
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #954

    • Property Keywords revocation research added
    • Property Summary changed from revoke write authority to revocable write authority
    • Property Type changed from defect to enhancement
    • Property Milestone changed from undecided to soon

  • Ticket #954 – Description

    initial v9  
    1 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.
     1As described in [/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.
    22
    33The 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).