From e18e5b3d2559f5f0395ffe79416cdca3abc89310 Mon Sep 17 00:00:00 2001
From: Rob Austein <sra@hactrn.net>
Date: Sun, 14 Feb 2021 16:01:15 +0000
Subject: Start restructuring for Pelican

---
 wiki/AssuredTooChain.trac | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 wiki/AssuredTooChain.trac

(limited to 'wiki/AssuredTooChain.trac')

diff --git a/wiki/AssuredTooChain.trac b/wiki/AssuredTooChain.trac
new file mode 100644
index 0000000..e4cd7ab
--- /dev/null
+++ b/wiki/AssuredTooChain.trac
@@ -0,0 +1,14 @@
+= 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
-- 
cgit v1.2.3