[prev in list] [next in list] [prev in thread] [next in thread]
List: cap-talk
Subject: Re: [EROS-Arch] Fw: [Cap-Talk] Re: On the other hand (process tool restriction)
From: "Jonathan S. Shapiro" <shap () eros-os ! org>
Date: 2000-11-09 22:11:23
[Download RAW message or body]
> >Is it necessary for it to be read only, or is it sufficient if you have
to
> >know the old one to overwrite it?
>
> (You must mean write-once instead of read-only above.) :-)
I mean write-multiple, but on any given write you must know the current
value in order to overwrite the slot. The main advantage of this is that it
doesn't require keeping a write counter.
> Before storing, you
> would want a strong assurance that the domain key was a domain key and not
> a Trojan stealing your brand key.
I should think that the process tool should simply refuse to perform the
operation on anything not a process capability.
_______________________________________________
cap-talk mailing list
cap-talk@mail.eros-os.org
http://www.eros-os.org/mailman/listinfo/cap-talk
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic