#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:
---------------------------------------------+------------------------------
Changes (by davidsarah):
* keywords: integrity => integrity forward-compatibility
Comment:
Replying to [comment:7 warner]:
> I guess it comes down to how we deal with caps-from-the-future. We can't
distinguish between mutable-caps-from-the-future and immutable-caps-from-
the-future, since we can't figure out anything about caps-from-the-future
other than the fact that we don't understand them. So if we want to
promise users who are listing an immutable directory that they'll only see
immutable caps, we'd have to filter out anything that we don't explicitly
recognize as immutable, which means removing all caps-from-the-future.
Not necessarily. If the directory is immutable, we could just omit
{{{rw_uri}}}.
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/833#comment:8>
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
