[cap-talk] Iguana First Release - revocation, Iguana user manual?
Karp, Alan H
alan.karp at hp.com
Tue Nov 29 23:33:22 EST 2005
> By making it impossible to communicate a capability you make
> it impossible
> to request services that require the capability (not direct
> invocations, but
> use by some component service) - unless the intended sender
> proxies the
> capability. Doing so is awkward and inefficient. To not do
> so means that
> the capability can't be shared which creates an awkward bound on the
> amount of modularity systems can utilize as they may not be
> able to pass
> needed capabilities between POLA divided parts of a service.
Nothing says the clist must have more than one entry. Since the
capability to the clist can be passed around, you haven't lost any
functionality or granularity. You can think of the clist as the
mechanism you use to revoke the capability it contains.
Virus Safe Computing Initiative
1501 Page Mill Road
Palo Alto, CA 94304
(650) 857-3967, fax (650) 857-7029
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Karp, Alan H.vcf
Size: 433 bytes
Desc: Karp, Alan H.vcf
Url : http://eros.cs.jhu.edu/pipermail/cap-talk/attachments/20051129/de00f0cc/KarpAlanH.vcf
More information about the cap-talk