proomt

Search

Search posts, papers, and topics

Hall of Fame

Hall of FameKen Thompson19849 min readtalkintermediate

Reflections on Trusting Trust

Read on cmu.edu

Summary

Ken Thompson’s Turing Award lecture shows how a compiler can be subverted to insert a hidden backdoor that survives source‑level inspection, and how self‑reproducing code can propagate such Trojan horses. The moral is that you can’t trust binaries you didn’t build yourself.

  • A compiler can embed a self‑replicating Trojan that re‑inserts itself each time it compiles, even if the source looks clean.
  • Binary‑only distribution is unsafe; reproducible builds are essential for security.
  • Self‑reproducing programs illustrate how hidden code can propagate automatically.
  • The attack can be applied at any layer, from compilers to microcode, making detection increasingly hard.

Anyone responsible for compiler toolchains, CI pipelines, or software supply‑chain security should understand this classic attack to protect against hidden backdoors.

9/10
securitycompilersprogramming languagessoftware supply chaintrust

Related reading

  1. Trusting-Trust Attack against an Entire Linux Distribution through Binary Manipulation

    The authors show that the classic trusting‑trust attack is not limited to compilers: by tampering with GNU strip they can inject a payload that propagates through NixOS's bootstrap and ends up in almost every binary of the final system. The attack succeeds on a real nixpkgs revision, building a full graphical installer while backdooring the majority of its binaries.

    arXiv cs.SE (Software Engineering)arxiv.org1 minpaperHN24159

  2. Who Owns AI-Generated Code Failures?

    AI‑generated code breaks the traditional chain of ownership: developers merge PRs they didn’t write, reviewers approve logic they didn’t originate, and QA validates tests chosen by a model. A CloudBees survey shows 81% of firms see more production failures from AI code, and accountability often drifts upward to CTO/VP. The post argues role‑based accountability isn’t enough; you need end‑to‑end tr…

    Codeshipcloudbees.com4 min

  3. The Shadow Factory: Why Your CI/CD Sprawl is About to Move Faster Than You Can Think

    The article warns that unchecked CI/CD sprawl— orphaned pipelines, hard‑coded secrets, and permissive runners— creates a hidden attack surface, and that AI‑driven agents will amplify the problem. It recommends a governance layer with real‑time inventory, policy‑as‑code, and AI guardrails to bring the software factory under the same security rigor as production.

    Codeshipcloudbees.com3 min

  6. Grounded Skill Synthesis from Code at Scale for Agentic Intelligence

    Code2Skill is an automated pipeline that mines popular GitHub repositories to extract verifiable, implementation‑anchored procedural “skills”. It builds a bank of ~1 M skill records (atomic ops, workflows, patterns) with provenance metadata, verifies each via blind reconstruction, and shows that augmenting LLM‑based agents with these skills yields an average 11.7% performance lift across 72 proto…

    Hugging Face Daily Papersarxiv.org1 minpaper