News for hackers. Stuff that matters.
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?
Re:A public TrueCrypt Audit by bmm6o on Wednesday October 09, 2013 @05:57PM (#6524159)
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.
Re:A public TrueCrypt Audit by antocv on Thursday October 10, 2013 @05:19AM (#6526489)
Then compile it with gcc on cygwin and/or llvm and compare.
Re:A public TrueCrypt Audit by cbr on Thursday October 10, 2013 @08:09AM (#6526966)
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.
Re:A public TrueCrypt Audit by skyn3e on Wednesday October 09, 2013 @06:33PM (#6524356)
It can easily be reverse engineered.