mailing list archives
How I Compiled TrueCrypt For Windows and Matched the Official Binaries
From: Xavier de Carné de Carnavalet <x_decarn () encs concordia ca>
Date: Sun, 27 Oct 2013 14:51:17 -0400
TrueCrypt is a popular piece of software enabling data protection by
means of encryption for all categories of users. It is getting even
more attention lately, following the revelations about the NSA, as the
authors remain anonymous and no thorough security audit have yet been
conducted to prove it is not backdoored in any way. This has led
several concerns raised in different places, such as this blog post
, this one , this security analysis , also related on that
blog post  from which IsTrueCryptAuditedYet?  was born. One of
the recurring questions is: What if the binaries provided on the
website were different than the source code and they included hidden
features? To address this issue, I built the software for Windows from
the official sources in a careful way and was able to match the
official binaries. According to my findings, all three recent major
versions (v7.1a, v7.0a, v6.3a) exactly match the sources.
Details on how to reproduce the results are mentioned at
- Does it mean TrueCrypt isn't backdoored in any way and is safe/secure?
- Does it mean a potential backdoor or weakness should only be found
in the source code?
Assuming you trust the compiler not to do anything wrong, yes.
- Nobody audited the source code.
True, so you should support IsTrueCryptAuditedYet? for this to happen.
Don't trust me, compile it yourself the way I did. If official
binaries get changed in the future, I can't vouch for them. Check
authenticity and integrity.
Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia - http://secunia.com/
- How I Compiled TrueCrypt For Windows and Matched the Official Binaries Xavier de Carné de Carnavalet (Oct 27)