aboutsummaryrefslogtreecommitdiff
path: root/content/AssuredTooChain.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/AssuredTooChain.md')
-rw-r--r--content/AssuredTooChain.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/content/AssuredTooChain.md b/content/AssuredTooChain.md
new file mode 100644
index 0000000..f3d6f25
--- /dev/null
+++ b/content/AssuredTooChain.md
@@ -0,0 +1,20 @@
+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.