id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
954	revocable write authority	zooko		"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.

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)."	enhancement	new	major	soon	code-mutable	1.6.0		integrity capleak forward-compatibility newcaps revocation research