#833: reject mutable children when *reading* an immutable dirnode
---------------------------------------------+------------------------------
Reporter: warner | Owner: warner
Type: defect | Status: assigned
Priority: critical | Milestone: 1.6.0
Component: code-dirnodes | Version: 1.5.0
Keywords: integrity forward-compatibility | Launchpad_bug:
---------------------------------------------+------------------------------
Comment(by zooko):
You know, we really ''should'' include an {{{imm_uri}}}, shouldn't we? I
guess the way we are currently doing it means "If you are listing a
mutable dir, then the {{{ro_uri}}} is a mutable child, and if you are
listing an immutable dir, then the {{{ro_uri}}} is an immutable child.".
Is that right? But what if there is an immutable child in a mutable dir?
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/833#comment:11>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
_______________________________________________
tahoe-dev mailing list
[email protected]
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
