Using Sparse Capabilities in a Distributed Operating System

Andrew S. Tanenbaum; Sape J. Mullender; Robbert van Renesse

Using Sparse Capabilities in a Distributed Operating System

Andrew S. Tanenbaum, Sape J. Mullender, Robbert van Renesse

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › Academic › peer-review

84 Citations (Scopus)

47 Downloads (Pure)

Abstract

Most distributed operating systems constructed to date have lacked a unifying mechanism for naming and protection. In this paper we discuss a system, Amoeba, that uses capabilities for naming and protecting objects. In contrast to traditional, centralized operating systems, in which capabilities are managed by the operating system kernel, in Amoeba all the capabilities are managed directly by user code. To prevent tampering, the capabilities are protected cryptographically. The paper describes a variety of the issues involved, and gives four different ways of dealing with the access rights.

Original language	English
Title of host publication	Proceedings of the 6th International Conference on Distributed Computing Systems 1986
Place of Publication	Los Alamitos, CA
Publisher	IEEE
Pages	558-563
Number of pages	6
Publication status	Published - May 1986
Event	6th International Conference on Distributed Computing Systems, ICDCS 1986 - Cambridge, United States Duration: 19 May 1986 → 23 May 1986 Conference number: 6

Conference

Conference	6th International Conference on Distributed Computing Systems, ICDCS 1986
Abbreviated title	ICDCS
Country/Territory	United States
City	Cambridge
Period	19/05/86 → 23/05/86

Access to Document

Tanenbaum1986usingFinal published version, 45.7 KB

Cite this

@inproceedings{3246f727e73243988ba4c8f1a1ad64f1,

title = "Using Sparse Capabilities in a Distributed Operating System",

abstract = "Most distributed operating systems constructed to date have lacked a unifying mechanism for naming and protection. In this paper we discuss a system, Amoeba, that uses capabilities for naming and protecting objects. In contrast to traditional, centralized operating systems, in which capabilities are managed by the operating system kernel, in Amoeba all the capabilities are managed directly by user code. To prevent tampering, the capabilities are protected cryptographically. The paper describes a variety of the issues involved, and gives four different ways of dealing with the access rights.",

author = "Tanenbaum, {Andrew S.} and Mullender, {Sape J.} and {van Renesse}, Robbert",

note = "Imported from DIES; 6th International Conference on Distributed Computing Systems, ICDCS 1986, ICDCS ; Conference date: 19-05-1986 Through 23-05-1986",

year = "1986",

month = may,

language = "English",

pages = "558--563",

booktitle = "Proceedings of the 6th International Conference on Distributed Computing Systems 1986",

publisher = "IEEE",

address = "United States",

}

Using Sparse Capabilities in a Distributed Operating System. / Tanenbaum, Andrew S.; Mullender, Sape J.; van Renesse, Robbert.
Proceedings of the 6th International Conference on Distributed Computing Systems 1986. Los Alamitos, CA: IEEE, 1986. p. 558-563.

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › Academic › peer-review

TY - GEN

T1 - Using Sparse Capabilities in a Distributed Operating System

AU - Tanenbaum, Andrew S.

AU - Mullender, Sape J.

AU - van Renesse, Robbert

N1 - Conference code: 6

PY - 1986/5

Y1 - 1986/5

N2 - Most distributed operating systems constructed to date have lacked a unifying mechanism for naming and protection. In this paper we discuss a system, Amoeba, that uses capabilities for naming and protecting objects. In contrast to traditional, centralized operating systems, in which capabilities are managed by the operating system kernel, in Amoeba all the capabilities are managed directly by user code. To prevent tampering, the capabilities are protected cryptographically. The paper describes a variety of the issues involved, and gives four different ways of dealing with the access rights.

AB - Most distributed operating systems constructed to date have lacked a unifying mechanism for naming and protection. In this paper we discuss a system, Amoeba, that uses capabilities for naming and protecting objects. In contrast to traditional, centralized operating systems, in which capabilities are managed by the operating system kernel, in Amoeba all the capabilities are managed directly by user code. To prevent tampering, the capabilities are protected cryptographically. The paper describes a variety of the issues involved, and gives four different ways of dealing with the access rights.

M3 - Conference contribution

SP - 558

EP - 563

BT - Proceedings of the 6th International Conference on Distributed Computing Systems 1986

PB - IEEE

CY - Los Alamitos, CA

T2 - 6th International Conference on Distributed Computing Systems, ICDCS 1986

Y2 - 19 May 1986 through 23 May 1986

ER -

Using Sparse Capabilities in a Distributed Operating System

Abstract

Conference

Access to Document

Fingerprint

Cite this