Printer-Friendly
Version
|
Next: References
Up: 03-caps
Previous: Sparse Capabilities
Subsections
- Passwords must be protected (eavesdropping, Trojan horses).
- Separate passwords for different rights (good idea to package
rights with caps).
- No encryption
==> easy to validate.
- Validation done by kernel on access or presentation and cached by MMU.
- Propagation easy, as capabilities are ``normal'' data.
- Restriction requires kernel to make new capability.
- Revocation done by kernel removing entry from object table.
- Amplification possible similar to AS/400.
- Accessibility is impossible to determine.
- Protection domain is known to kernel.
- Statistically secure (like encryption).
- Validation at mapping time
==> applications can use
``normal'' pointers.
- Validation may be slow, but kernel and MMU can cache.
- No kernel intervention required on most operations.
- Reference counting impossible to detect unaccessible objects.
Gernot Heiser
2002-08-15
|