[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Wrapper design patterns (was: Revocation vs destruction)
|
From: |
Pierre THIERRY |
|
Subject: |
Re: Wrapper design patterns (was: Revocation vs destruction) |
|
Date: |
Tue, 29 Nov 2005 15:17:35 +0100 |
|
User-agent: |
Mutt/1.5.9i |
Scribit Jonathan S. Shapiro dies 18/10/2005 hora 15:58:
> In principle, we could do something similar for capabilities that
> travel from one user to another -- any time a capability crosses this
> boundary it's wrapper is replaced. This replacement is implemented by
> a reference monitor.
How does the system knows you cross the boundary? If a process belonging
to a different user gets the capability, how does anyone know it is in
fact a different user?
Curiously,
Nowhere man
--
address@hidden
OpenPGP 0xD9D50D8A
signature.asc
Description: Digital signature
- Re: Wrapper design patterns (was: Revocation vs destruction),
Pierre THIERRY <=