diff options
author | Rob Austein <sra@hactrn.net> | 2021-02-14 16:01:15 +0000 |
---|---|---|
committer | Rob Austein <sra@hactrn.net> | 2021-02-14 16:01:15 +0000 |
commit | e18e5b3d2559f5f0395ffe79416cdca3abc89310 (patch) | |
tree | 340bdc43c4bfa7bcc3c048eea4db848cabe470de /pelican/content/AssuredTooChain.md | |
parent | ad1cc0517983e599897929b4c94463bf2af78f7c (diff) |
Start restructuring for Pelican
Diffstat (limited to 'pelican/content/AssuredTooChain.md')
-rw-r--r-- | pelican/content/AssuredTooChain.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/pelican/content/AssuredTooChain.md b/pelican/content/AssuredTooChain.md new file mode 100644 index 0000000..89ea7d9 --- /dev/null +++ b/pelican/content/AssuredTooChain.md @@ -0,0 +1,16 @@ +# 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. |