summaryrefslogtreecommitdiff
path: root/raw-wiki-dump/AssuredTooChain.md
diff options
context:
space:
mode:
Diffstat (limited to 'raw-wiki-dump/AssuredTooChain.md')
-rw-r--r--raw-wiki-dump/AssuredTooChain.md16
1 files changed, 0 insertions, 16 deletions
diff --git a/raw-wiki-dump/AssuredTooChain.md b/raw-wiki-dump/AssuredTooChain.md
deleted file mode 100644
index 89ea7d9..0000000
--- a/raw-wiki-dump/AssuredTooChain.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# Issues of an Assured Tool-Chain
-
-We do not have any assurance that our basic tools are not compromised.
-
-* Compilers
-* Operating Systems
-* Hardware Platforms
-* Verilog and Other Tools to Produce Chips
-
-
-At the base, is the compiler. The fear was first formally expressed in
-Ken Thompson's 1984 Turing Award Lecture
-[Reflections on Trusting Trust](http://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf).
-
-David A. Wheeler's PhD thesis, [Fully Countering Trusting Trust through Diverse Double-Compiling](http://www.dwheeler.com/trusting-trust/)
-outlines how we might deal with the compiler trust conundrum.