Changes between Version 9 and Version 10 of Ticket #954
- Timestamp:
- 2013-12-27T23:48:24Z (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #954 – Description
v9 v10 1 As 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.1 As 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. 2 2 3 3 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).
