Talk:Object-capability model
Appearance
To do:
- Add etymology to introduction
- The name comes from recognition of the fact that "pure" object-oriented programming constitutes the capability-based security model.
- Touted advantages of objects (encapsulation, modularity) are precisely what we want for security (privilege separation, least privilege).
- Section: Relationship to object-oriented programming
- references are called "pointers"
- Section: Relationship to capability-based security
- references are called "capabilities"
- Section: Combining designation and authority
- Section: Graph connectivity
- Show the Granovetter diagram!
- Only connectivity begets connectivity
- Section: The term "capability"
- object-capabilities versus password capabilities