aboutsummaryrefslogtreecommitdiff
path: root/pelican/content/AssuredTooChain.md
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2021-10-08 00:30:08 -0400
committerRob Austein <sra@hactrn.net>2021-10-08 00:30:08 -0400
commit71487660812754e5f26f26595b6c3d456f9f6db8 (patch)
treee960190262edcbb0164edbac1e52915c5a339442 /pelican/content/AssuredTooChain.md
parentb11298b250f63daf091591d1638608325f766d9a (diff)
Get rid of conversion stuff, just build content -> website
Diffstat (limited to 'pelican/content/AssuredTooChain.md')
-rw-r--r--pelican/content/AssuredTooChain.md20
1 files changed, 0 insertions, 20 deletions
diff --git a/pelican/content/AssuredTooChain.md b/pelican/content/AssuredTooChain.md
deleted file mode 100644
index f3d6f25..0000000
--- a/pelican/content/AssuredTooChain.md
+++ /dev/null
@@ -1,20 +0,0 @@
-Title: AssuredTooChain
-Author: trac
-Date: 2016-12-15 22:44
-
-# 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.