4 ms·
>My default assumption is that anything I can't see the source code of and compile myself is compromised. Did you also write and compile the compiler that comp
by blhack 13y ago
>My default assumption is that anything I can't see the source code of and compile myself is compromised.
Did you also write and compile the compiler that compiled your compiler?
- justinreeves 13y agoHe very well may have, since you compile gcc using gcc.
- blhack 13y agoAnd where did the bin version of GCC he or she used to compile that version of GCC come from? Eventually, somewhere down the chain, you have to have trusted a compiler that wasn't GCC and you probably don't have the source to.
- marcell 13y agoDiff the binaries :)
- KnightHawk3 13y agoIf they really want to get you they could use a birthday attack? Since we are talking about checking the compiler that compiles your compiler here.
- gohrt 13y agoWhich a diff tool you compiled your self, or looking at the hard drive with a magnifying glass?
- willvarfar 13y agoI think blhack was referring to Ken Thompson's ACM Turing Award acceptance speech "Reflections On Trusting Trust"? http://c2.com/cgi/wiki?TheKenThompsonHack http://c2.com/cgi/wiki?TheKenThompsonHack "a hack (in every sense), the most subversive ever perpetrated, nothing less than the root password of all evil." A very very good read :)