Ken Thompson, 1983: wouldn't it be awful if someone snuck secret code into a compiler that broke our ability to trust the output of a computer
-
Ken Thompson, 1983: wouldn't it be awful if someone snuck secret code into a compiler that broke our ability to trust the output of a computer
AI Guy, 2026: wouldn't it be cool if we stuck something we know can't be trusted into every part of the computer
-
Ken Thompson, 1983: wouldn't it be awful if someone snuck secret code into a compiler that broke our ability to trust the output of a computer
AI Guy, 2026: wouldn't it be cool if we stuck something we know can't be trusted into every part of the computer
@ricci For those who didn't do Computing Science (which is different to "coding" or "programming") the paper is at https://dl.acm.org/doi/10.1145/358198.358210
Literally EVERY computer user for a generation *should* have read this. Few have. Fewer have understood it. -
@ricci For those who didn't do Computing Science (which is different to "coding" or "programming") the paper is at https://dl.acm.org/doi/10.1145/358198.358210
Literally EVERY computer user for a generation *should* have read this. Few have. Fewer have understood it.@WellsiteGeo @ricci Wrong reference! It's p. 52 (PDF p. 56) of https://seclab.cs.ucdavis.edu/projects/history/papers/karg74.pdf#?page=56 (1974).
-
@ricci For those who didn't do Computing Science (which is different to "coding" or "programming") the paper is at https://dl.acm.org/doi/10.1145/358198.358210
Literally EVERY computer user for a generation *should* have read this. Few have. Fewer have understood it.@WellsiteGeo @ricci I haven't read the paper but there's an excellent discussion of it for laypeople in the book "Your computer is on fire." Highly recommend.
-
R reynir@social.data.coop shared this topic
