[cap-talk] Persistence as a cap value

[Pierre THIERRY]

Scribit James A. Donald dies 14/03/2008 hora 11:45:
> Jed Donnelley wrote:
>> I wonder if you could give an example of a capability that made sense
>> to issue/communicate as non-persistent? [...] 
> The capability to access a particular file: my word processor should
> not be able to open or modify any @#$%^&* file it pleases,

I don't see how persistence of a file capability could enable the
process holding it to access "any file it pleases". If the process
receives from a powerbox a persistent read/write capability to a file X,
at each restart of the system it will only be able to read and write
file X.

And if I have started a dozen editors on source files and three help
viewers on various documentations, I don't want to have to reopen them
on restart. I don't even want to have to remember what was open.

Persistently,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://www.eros-os.org/pipermail/cap-talk/attachments/20080314/f2d77eb3/attachment.bin