Jack Dennis — The Forgotten Origin of Capabilities

<!-- hierarchy:nav -->

Path: OIP › Thinker Reference › Thinkers › Jack Dennis — The Forgotten Origin of Capabilities

Shelf: Thinkers · Traversal: self-explaining · hierarchical · voxel-ready
Machine root: OIP tree · Registry

Jack Dennis — The Forgotten Origin of Capabilities

§SELF — thinker-jack-dennis

What this page is: A profile of Jack Dennis and his 1966 invention of capability-based addressing, the foundation of all capability security systems. What it explains: How Dennis's hardware memory protection model became the basis for modern software security architectures. Why read it: To understand where capability security came from and why separating access authority from program identity matters.

What Jack Dennis Is

Jack Dennis is a professor emeritus at the Massachusetts Institute of Technology (MIT — a university in Cambridge, Massachusetts, USA). He is a computer scientist who invented capability-based addressing in 1966. A "capability" (in computer security) is a token that grants permission to access a specific resource. The token itself carries the authority — whoever holds the token can use the resource.

Why It Matters

Before Dennis's work, computer security systems asked: "Who are you?" and then decided what you could access based on your identity. Dennis changed the question to: "What do you hold?" — meaning, what capability tokens do you possess? This separation of authority from identity became the foundation of capability security. Modern systems derived from Dennis's idea include: KeyKOS (a secure operating system built by Norm Hardy in the 1970s–80s), the E programming language (by Mark Miller, 1997), and seL4 (a formally verified operating system kernel, 2009). These systems are used in high-security environments because capability-based access control reduces the attack surface — there are fewer ways for an attacker to gain unauthorized access when permissions are tied to possession of specific tokens rather than to broad identity categories.

The Key Idea

Dennis's key idea, published in the 1966 paper "Segmentation and the Design of Multi-Programmed Computer Systems," was: memory segments (contiguous regions of computer memory) should carry permission bits indicating whether the holder can read, write, or execute that segment. A program can only access a segment if it holds a capability — a hardware-protected reference to that segment. The hardware enforces this: if a program tries to access memory without holding the corresponding capability, the hardware blocks the access. This is different from identity-based systems where the operating system checks a user's credentials against an access control list.

Dennis co-authored with Earl Van Horn the 1965 paper "Programming Semantics for Multiprogrammed Computations," which provided the theoretical foundation for this model by defining formal semantics (precise mathematical rules) for how concurrent programs interact with shared resources.

What He Got Right

• Separating access authority from program identity. In Dennis's model, a program's ability to access a resource depends only on whether it holds the capability for that resource — not on who created the program or what user account it runs under. This means capabilities can be transferred between programs freely without changing any central authority database.
• Hardware enforcement. Dennis designed the protection mechanism to be enforced by the computer's hardware (specifically, the memory management unit), not by software checks. Hardware enforcement cannot be bypassed by software bugs or malicious code.
• Fine-grained permissions. Each capability carries specific permissions (read, write, execute) for a specific memory segment. This is more precise than broad categories like "administrator" or "user."

What He Got Wrong or Left Unfinished

• Hardware capability machines were never mass-produced. Dennis's design required specialized hardware that was not built commercially. General-purpose computers used simpler memory protection schemes. Without the hardware, capability-based security remained a theoretical concept for decades.
• Software implementations were necessary but came later. Because the hardware was not adopted, researchers had to implement capability semantics in software. Norm Hardy's KeyKOS (built at Key Logic in the 1980s) was the first practical pure-capability operating system. Mark Miller's E language (1997) brought capabilities to distributed programming. These implementations proved the model works but required decades of additional engineering.
• No solution for capability revocation. Dennis's original model did not specify how to take back a capability once granted. If Program A gives Program B a capability to access a file, how can A later revoke that access? This problem was solved in later systems (KeyKOS used a mechanism called "segment keys" that could be invalidated), but Dennis's original paper did not address it.

How It Connects to Other Ideas

• Access control lists (ACLs). ACLs are the alternative to capabilities. In an ACL system, each resource has a list of who can access it. In a capability system, each subject has a list of what it can access. The two models are mathematically equivalent in expressive power but differ in practical properties: capabilities are easier to delegate (you hand over the token), while ACLs are easier to audit (you check one list to see who has access). Dennis's work established the capability side of this fundamental divide.
• Object-capability security (ocap). Modern secure programming languages like E and Caja use "object capabilities" — the same principle as Dennis's memory capabilities, but applied to software objects rather than hardware memory segments. An object can only call methods on another object if it holds a reference (capability) to it. This is a direct conceptual descendant of Dennis's 1966 design.
• OIP capability tokens. The Open Integrity Protocol (OIP) uses capability tokens as a web-native expression of Dennis's idea. In OIP, possession of a token grants access to a resource, and the token's permissions are scoped (limited in what they allow). This is the same structure as Dennis's hardware capabilities — a protected reference with embedded permissions — implemented as cryptographic tokens on the web instead of hardware memory references.

Sources

• Dennis, J. B. (1966). "Segmentation and the Design of Multi-Programmed Computer Systems." Journal of the ACM, 12(4), 589–602.
• Dennis, J. B., & Van Horn, E. C. (1966). "Programming Semantics for Multiprogrammed Computations." Communications of the ACM, 9(3), 143–155.

---

Up the tree

• OIP root — protocol root, zero-context entry
• Thinker Reference hub — full hierarchy map
• Thinkers shelf — siblings on this shelf
• Voxel graph article — how pages link as voxels
• Self-describing protocol

Related on this shelf

• Alan Kay — The Big Idea Is Messaging
• Alfred North Whitehead — Process and Reality
• J.L. Austin and John Searle — Speech Acts
• Barbara Liskov — Abstract Data Types and Distributed Consensus
• Bram Cohen — BitTorrent and Content-Addressed Protocol Design
• Butler Lampson — Protection and Access Control
• Carl Hewitt — The Actor Model
• Charles Sanders Peirce — Signs, Abduction, and Pragmatism

Machine surfaces

• Public page: https://miscsubjects.com/a/thinker-jack-dennis
• JSON article: https://miscsubjects.com/api/articles/thinker-jack-dennis
• OIP ask: https://miscsubjects.com/api/dispatch?ask=Jack%20Dennis%20%E2%80%94%20The%20Forgotten%20Origin%20of%20Capabilities