Linked by Thom Holwerda on Sat 4th Mar 2006 17:27 UTC, submitted by Tyr.
Permalink for comment 101488
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-07-11
rayiner: "The ability to compile the code (with a trusted compiler) is a requirement for being able to verify that the binaries you deploy match byte for byte the code produced by compiling"
(1) Rayiner you obviously don't understand what you are talking about - two different compilers will invariably produce two different binaries - this is because different compilers use different compilation strategies - this is obvious to any software developer.
If you then use the same compiler(s) as microsoft how will you know that the compiler hasn't inserted bad code?
If both use GCC, then you won't be comparing against the original binary.
If you use GCC, you binaries will be different because the compilers are different and how do you know the compiler didn’t insert bad code anyway?
The GNU project servers were compromised for 4 months undetected.
http://uk.builder.com/manage/work/0,39026594,20277728,00.htm
Truly the only way to verify a binary is to decompile and debug.
(2) Quote: "The kernel code is written primarily in C, with assembly code reserved for those tasks that require the fastest possible code or that really heavily on the capabilities of the processor" - Inside NT Kernel Architecture
Edited 2006-03-05 09:54