ALT-18 · Paper · 23 Oct 2026
Reflections on Trusting Trust: the compiler that lies
Ken Thompson's 1984 Turing Award lecture described a backdoor that hides in the compiler and survives a full review of the source. Forty years later it is the reason reproducible builds exist.
- Aug 1984“Reflections on Trusting Trust” published in Communications of the ACM.
- 2005–2009David A. Wheeler proposes and proves Diverse Double-Compiling as a countermeasure.
- 2013–The Reproducible Builds movement makes identical binaries from identical sources a practical goal.
The idea
A compiler is itself a program built by a compiler. Teach it to recognise two things — the login program and its own source — and to add a backdoor to the first and the backdoor-adding code to the second. After one bootstrapping step, the source of both is clean and the binaries are not.
Why it still matters
Every modern software supply chain is a longer version of Thompson's chain: compilers, build servers, package registries, CI. The defences — independent rebuilds, diverse toolchains, signed provenance — exist because of this lecture.
Our reading
Analysis — Altumptic's interpretation of the sources below.
- Reviewing source code proves less than it feels like it proves.
- Reproducible builds turn “trust us” into “check us”.
- The build system is part of the attack surface, not plumbing.
What it means for you
- Make builds reproducible, and have someone else reproduce them.
- Pin and verify toolchains rather than taking whatever the image ships.
- Publish build provenance (attestations) alongside releases.
Sources
- Ken Thompson — Reflections on Trusting Trust, CACM 1984 (ACM DL)
- David A. Wheeler — Countering Trusting Trust through Diverse Double-Compiling
- Reproducible Builds
Altumptic was not involved in this research. Figures are as published by the sources above.
Cite this entry
Altumptic Lab (2026). ALT-18 — Reflections on Trusting Trust: the compiler that lies. 23 Oct 2026. altumptic.com/research/trusting-trust-1984