Re:A public TrueCrypt Audit
by jl6 on Wednesday October 09, 2013 @04:33PM
(#6523652)
Plus I guess Visual Studio could be backdoored to recognise the TrueCrypt source code and insert malicious code?
[ Parent
| on HN ]
Not only technically very difficult, but requires the MS VC++ team to be complicit and silent. I'd put it pretty far down the list.
Re:A public TrueCrypt Audit
by DigitalJack on Wednesday October 09, 2013 @08:11PM
(#6524827)
Not that hard to imagine anymore, with National Security Letters and whatnot.
Then compile it with gcc on cygwin and/or llvm and compare.
Then it won't match. Your only hope of getting exactly the same binary is to use the same compiler with all the same settings.