#833: reject mutable children when *reading* an immutable dirnode
------------------------------------------------------------------------------------+
Reporter: warner
| Owner: davidsarah
Type: defect
| Status: assigned
Priority: critical
| Milestone: 1.6.0
Component: code-dirnodes
| Version: 1.5.0
Keywords: integrity forward-compatibility backward-compatibility
confidentiality | Launchpad_bug:
------------------------------------------------------------------------------------+
Comment(by davidsarah):
I've put the prefixes in READONLY_PREFIX and IMMUTABLE_PREFIX constants,
so this would be trivial to change. I have no strong opinion on whether to
use "{{{ro.}}}" and "{{{imm.}}}" vs "{{{readonly.}}}" and
"{{{immutable.}}}".
I understand the reasons for nervousness, but we're getting quite a lot of
forward-compatibility goodness from this set of changes, and we should
have sufficient time to review it before the release.
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/833#comment:38>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
_______________________________________________
tahoe-dev mailing list
tahoe-dev@allmydata.org
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
