Book contents
- Frontmatter
- Contents
- Author Biographies
- Acknowledgments
- Dialogues Trust, Computing, and Society: Introduction
- Part 1 The Topography of Trust and Computing
- 2 The Role of Trust in Cyberspace
- 3 The New Face of the Internet
- 4 Trust as a Methodological Tool in Security Engineering
- Part 2 Conceptual Points of View
- Part 3 Trust in Design
- References
- Index
4 - Trust as a Methodological Tool in Security Engineering
from Part 1 - The Topography of Trust and Computing
Published online by Cambridge University Press: 05 March 2014
- Frontmatter
- Contents
- Author Biographies
- Acknowledgments
- Dialogues Trust, Computing, and Society: Introduction
- Part 1 The Topography of Trust and Computing
- 2 The Role of Trust in Cyberspace
- 3 The New Face of the Internet
- 4 Trust as a Methodological Tool in Security Engineering
- Part 2 Conceptual Points of View
- Part 3 Trust in Design
- References
- Index
Summary
Introduction
Ken Thompson was the 1984 recipient of the Turing Award, the equivalent of the Nobel Prize in Computer Science. His recognized contributions include the design, while at Bell Labs, of the UNIX operating system, that later led to the free software flagship Linux, and today Android, which has the largest share of the smartphone market. Yet, in his acceptance address, Thompson did not choose to talk about operating system design, but instead about computer security, and specifically “trust.” His thoughts were later collected in an essay entitled “Reflections on Trusting Trust” (Thompson, 1984), which has become a classic in the computer security literature. In this work, Thompson examines to what extent one can trust – in an intuitive sense, but as we will see, also a technical sense – a computer system. He recounts how computer systems are built on layers of hardware, but also by layers of software – computer code that provide instructions for how they should perform high-level operations, such as writing a document or loading a Web page. How could anyone foresee what these devices could do under different circumstances? First, they would have to examine what the hardware would do under all conditions. Although this is expensive, it is possible, as hardware is composed of fixed arrangements of wires, silicon, and plastic. Naively, one could assume that software could also be examined in a similar fashion: by reading the source code of the software to understand how it would behave.
- Type
- Chapter
- Information
- Trust, Computing, and Society , pp. 68 - 92Publisher: Cambridge University PressPrint publication year: 2014
- 4
- Cited by