News for hackers. Stuff that matters.
Re:Prism Break by blhack on Tuesday July 09, 2013 @01:09AM (#6011220)
>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?

Re:Prism Break by justinreeves on Tuesday July 09, 2013 @01:19AM (#6011238)
He very well may have, since you compile gcc using gcc.
Re:Prism Break by willvarfar on Tuesday July 09, 2013 @02:34AM (#6011413)
I think blhack was referring to Ken Thompson's ACM Turing Award acceptance speech "Reflections On Trusting Trust"?

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 :)

Re:Prism Break by blhack on Tuesday July 09, 2013 @01:20AM (#6011240)
And 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.

Re:Prism Break by marcell on Tuesday July 09, 2013 @01:48AM (#6011300)
Diff the binaries :)
Re:Prism Break by gohrt on Tuesday July 09, 2013 @02:15AM (#6011360)
Which a diff tool you compiled your self, or looking at the hard drive with a magnifying glass?
Re:Prism Break by KnightHawk3 on Tuesday July 09, 2013 @02:07AM (#6011351)
If 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.