[e-lang] [cap-talk] File API taming

[ihab.awad at gmail.com]

I should clarify some vagueness that was caught by David Wagner --

On Thu, Apr 9, 2009 at 4:34 PM, <ihab.awad at gmail.com> wrote:

> * Files provide a "getPath()" up to the closest makeOpaque()-ed directory;
> and
>
> * Each sandbox gets a reference to a (usually -- but not always --
> makeOpaque()-ed) reference to a directory that serves as its "chroot()-ed
> jail".
>

One more criterion is that no directory (makeOpaque()-ed or not) can
resolves a ".." path that traverses past its own level. So, for directory
'd', the following work --

  d.resolve('foo/bar');
  d.resolve('baz');
  d.resolve('a/b/../c');

but not --

  d.resolve('..');
  d.resolve('a/b/../../..');

Ihab

-- 
Ihab A.B. Awad, Palo Alto, CA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/e-lang/attachments/20090409/62f1b253/attachment-0001.html