summaryrefslogtreecommitdiff
path: root/raw-wiki-dump/AssuredTooChain
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2020-09-13 23:06:24 +0000
committerRob Austein <sra@hactrn.net>2020-09-13 23:06:24 +0000
commit891730d13b324fad916572a82f0bd610c5de9aad (patch)
treef46c94ddfff34f15aafe7cac0596716d1c13c412 /raw-wiki-dump/AssuredTooChain
parentb092ffbcbe2c9398494f7dc9db6f0796971633e0 (diff)
Rename for conversion
Diffstat (limited to 'raw-wiki-dump/AssuredTooChain')
-rw-r--r--raw-wiki-dump/AssuredTooChain14
1 files changed, 0 insertions, 14 deletions
diff --git a/raw-wiki-dump/AssuredTooChain b/raw-wiki-dump/AssuredTooChain
deleted file mode 100644
index e4cd7ab..0000000
--- a/raw-wiki-dump/AssuredTooChain
+++ /dev/null
@@ -1,14 +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
-[http://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf Reflections on Trusting Trust].
-
-David A. Wheeler's PhD thesis, [http://www.dwheeler.com/trusting-trust/ Fully Countering Trusting Trust through Diverse Double-Compiling]
-outlines how we might deal with the compiler trust conundrum. \ No newline at end of file