Suggesting people use Bitlocker is completely against everything they stand for. Here are some quotes off the FAQ on OP's rehosted website:
> > Will TrueCrypt be open-source and free forever?
> Yes, it will. We will never create a commercial version of TrueCrypt, as we believe in open-source and free security software.
> > Why is TrueCrypt open-source? What are the advantages?
> As the source code for TrueCrypt is publicly available, independent researchers can verify that the source code does not contain any security flaw or secret ‘backdoor’. If the source code were not available, reviewers would need to reverse-engineer the executable files. However, analyzing and understanding such reverse-engineered code is so difficult that it is practically impossible to do (especially when the code is as large as the TrueCrypt code).
> Remark: A similar problem also affects cryptographic hardware (for example, a self-encrypting storage device). It is very difficult to reverse-engineer it to verify that it does not contain any security flaw or secret ‘backdoor’.
These same people who condemned closed-source crypto in their FAQ are now suggesting using a closed-source encryption suite? It is completely absurd, and that's the point.
I could never believe otherwise. Not after everything I've learned in my time on this rock.
Nobody would expect the TrueCrypt devs to recommend something like this, so it is immediately suspect and all anyone really needs to asusme something isn't right (like a gag order).
Developers don't abruptly shut down projects. If there are problems with the code, they release statements and patches. If they lose interest in the project, they call it orphaned and ask for maintainers. If it's a mix of the two, they at least say so.
But what happened with TrueCrypt was truly bizarre. No warning. No phase-out. Telling people to move to BitLocker?
I think there's only one way to interpret that. They did something bizarre because it was all the noise they could make without telling us what really happened. AKA some of their developers got served gag orders.
But what on earth could a TrueCrypt dev be gagged for? A gag order implies that some three-letter-agency had enough foresight to know they were planning to disclose something. If it was that there was a government backdoor in TrueCrypt itself, how would NSA/FBI know that they discovered it? How would they know that it could be tied back to them? Why didn't the audit [1] catch it? Gag orders are pretty loose in terms of legality in the first place, but even still, would a gag order prevent them from releasing a statement about a security hole (without mentioning its origin) and releasing patches?
It's a total guess, but my theory is that TrueCrypt discovered something outside their codebase (EG: Windows itself) that was undermining encryption. They reached out to Microsoft, who contacted FBI/NSA, and they were served their gag orders. This is the only theory I can think of that makes a gag order possible, in other situations the FBI/NSA wouldn't have been able to know about a disclosure before it happened.
[1]: istruecryptauditedyet.com