

This means: under Windows, use Bitlocker. This has superior integration, so it tends to be easier to use and administer not only for single-OS users and administrator but even for dual-OS users. I said it before, and I'll say it again: the best solution, unless you have very specific requirements, is to use your operating system's native encryption mechanism. As the audit moves into its next phase, digging past the startup and boot loader and into the core crypto, updates will be posted and maintained here.


TrueCrypt Developer “David”: Said “Bitlocker is ‘good enough’ and Windows was original ‘goal of the project.’ ”.Steven Barnhart: “Also said no government contact except one time inquiring about a ‘support contract.’ ”.Steven Barnhart: “I asked and it was clear from the reply that "he" believes forking's harmful because only they are really familiar w/code.”.Steven Barnhart (Paraphrasing): Developer “personally” feels that fork is harmful: “The source is still available as a reference though.”.We worked hard on this for 10 years, nothing lasts forever.” Steven Barnhart wrote to an eMail address he had used before and received several replies from “David.” The following snippets were taken from a twitter conversation which then took place between Steven Barnhart and Matthew Green TrueCrypt Developer “David”: “We were happy with the audit, it didn't spark anything. To excerpt a key part of that article: And then the TrueCrypt developers were heard from. Yes, Virginia, TrueCrypt is still safe to use.
