[cap-talk] KeyKOS, EROS, CapROS keyInfo/databyte (was: Re: EQ, MyCap? review)
Jonathan S. Shapiro
shap at eros-os.com
Tue Feb 12 21:00:29 EST 2008
On Tue, 2008-02-12 at 17:13 -0800, Jed Donnelley wrote:
> I was able to find the databyte and Key Info fields in:
> and in:
> respectively, so that helps explains what was going on there.
> Since I believe I recall the KeyKOS, EROS, and CapROS capabilities
> are persistent, presumably you needed to use sufficient distinct
> "Key Info" values to distinguish from all possible past instances
> of capabilities...
Not necessary. Caps to destroyed objects become invalid because their
allocation count increments. Also, look at the specification of red
segments (KeyKOS) or wrappers (EROS). Not sure what Charlie has done in
CapROS. In Coyotos, Endpoints subsumed wrappers.
More information about the cap-talk