4 ms·
Revocation is a solved problem for pure capabilities [1,2]. Privilege escalation is typically not so important in capability systems because processes run with
by naasking 10y ago
Revocation is a solved problem for pure capabilities [1,2]. Privilege escalation is typically not so important in capability systems because processes run with least privileges. There is a pattern whereby authority can be increased if you're granted a special type of capability -- the operation is called "rights amplification" in capability parlance, but these capabilities are closely held by the trusted base.
Finally, the reason restricting delegation doesn't generally work is that a process can just proxy access to the undelegable capability, which means you haven't actually attentuated authority in any meaningful way. At best, you've merely reduced the bandwidth, so overall performance suffers, and you've also sacrificed compositional reasoning.
Anyway, that's why I initially asked for any design documents for Redox's capability system, so I encourage ticki and any others working on this to write a rough draft of the ideas. I know plenty of capability people who would happily provide feedback.
[1] https://www.cs.ucsb.edu/~chris/teaching/cs290/doc/eros-sosp99.pdf https://www.cs.ucsb.edu/~chris/teaching/cs290/doc/eros-sosp9...
[2] https://sel4.systems/Info/Docs/seL4-manual-2.0.0.pdf https://sel4.systems/Info/Docs/seL4-manual-2.0.0.pdf