Ramifications of Integrity {See (last) and (integ) also.}

{arcane}Notes on "Operating System Structures to Support Security and Reliable Software"

Designing, Describing and Implementing Security Policies

Who Holds What Keys?

(sdc)Slow Data Channels

Secure Communications

Suppose that we do not trust Tymnet but wish to use it. Suppose that we trust, instead, some particular ciphering algorithm such as DES (Data Encryption Standard). For now we shall ignore the problem of key management and assume a constant key for each terminal.

We assume that the key is protected in the terminals by locking them up. For each terminal n we construct a domain Dn that executes DES and holds the same key as the terminal.

{arcane}User Compartments

Transmission Control for Keys (The Guard)

Secret References to Unsecret Things

Other Security-related Parts of the Manual

See (cc) concerning copyability of capabilities.

See (revoke) about rescindable capabilities.

See (confine) about confinement and motivation for factories.

See (escrow) for some {possibly} more general ideas than factories.

See (p2,term-sec) about some terminal problems.

(audit)Auditing Access