TrueCrypt — The Honourable Shutdown?

1. What Actually Happened

On 28 May 2014, the official TrueCrypt website at truecrypt.sourceforge.net was replaced, without warning or prior announcement, by a single page that read:

The page recommended that Windows users move to BitLocker — Microsoft's closed-source, government-friendly disk-encryption product. A new binary, TrueCrypt 7.2, was released the same day. The 7.2 build could only decrypt existing volumes; encryption was completely disabled. Cryptographic signatures matched the previous TrueCrypt developer keys, so the shutdown was either an inside job or a very thorough compromise of those keys.

To users, security researchers, and the open-source community, the message was both shocking and obviously strange. TrueCrypt had been the gold-standard cross-platform disk encryption tool for over a decade. It was the recommended choice in Edward Snowden's leaked NSA training documents as an encryption tool the agency could not reliably break. And the developers had, just months earlier, been actively cooperating with an independent cryptographic audit that was finding no significant flaws.

The shutdown was so abrupt, so out of character, and so peculiarly worded that the entire security community immediately suspected it was something other than what it claimed to be.

2. Timeline

3. The Gag-Order Theory

Within hours of the shutdown, the dominant interpretation in the security community was that the developers had been served with a secret legal order — a National Security Letter, FISA §702 directive, UK Technical Capability Notice, or equivalent — demanding either backdoor cooperation or surrender of signing keys, and that they had chosen to terminate the project rather than comply. This theory rests on several specific signals.

A — The "warrant canary" reading

The shutdown notice itself contains language that no developer would write voluntarily. The phrase "TrueCrypt is not secure as it may contain unfixed security issues" is grammatically odd and factually unsupported by the audit work going on at the time. Some readings:

• "WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues" — the first letters of the operative phrase spell out "uti nsa im cu si" which, depending on how strict you are with Latin construction, can be parsed as "if I wish to use the NSA" or "do not use because the NSA". Cryptographers and Latin scholars disagreed on whether this was deliberate, but it was widely circulated as a plausible coded message.
• The blunt instruction to migrate to BitLocker, of all things — a closed-source Microsoft product known to have NSA-friendly Key Escrow features for enterprise deployment — was so wildly out of keeping with the developers' history that many read it as sarcastic on purpose, designed to scream "this isn't us" to anyone who knew them.

B — The behavioural signal

Developers who have been working publicly for ten years on a project, cooperating with an active audit, and shipping regular updates, do not silently disappear overnight without a single explanation, blog post, or signed-off message of farewell — unless they are legally prohibited from doing so.

National Security Letters in the US, Technical Capability Notices in the UK under the Investigatory Powers Act 2016 (or its 2014-era predecessor, RIPA), and FISA gag orders all share one core feature: the recipient cannot publicly acknowledge that the order exists. Telling friends, lawyers (outside the narrow privileged scope), journalists, or the public is a criminal offence. The recipient's options are:

1. Comply secretly
2. Challenge in the issuing court (rarely successful, never public)
3. Walk away from the activity that triggered the order

Option 3 — closing the project, destroying the keys, and refusing to continue — is consistent with everything observable about the TrueCrypt shutdown.

C — The Lavabit precedent

The TrueCrypt shutdown happened less than a year after the most well-documented public case of exactly this dynamic: Lavabit.

D — What the audit found (and didn't)

The Open Crypto Audit Project's results matter because they cut both ways:

• What was found: no intentional backdoors in the audited bootloader, kernel driver, or cryptographic primitives. Some implementation weaknesses (e.g., AES key schedule that could be slightly more resistant to cache-timing attacks; the RNG path on Windows had some less-than-ideal design choices). Nothing that would let an attacker passively decrypt a TrueCrypt volume.
• What was NOT found: any justification for the "not secure" framing of the shutdown notice. The audit's findings were public, peer-reviewed, and modest. They did not warrant the dramatic abandonment of a flagship encryption tool.

This mismatch — a mild audit verdict versus a wholesale "the product is not secure, walk away" public statement — is the strongest single argument that the public reason given was not the real one.

4. Counter-Arguments — Why the Gag-Order Theory Might Be Wrong

An honest assessment also has to engage with the reasons not to immediately accept the theory.

The honest position is that the gag-order theory is strongly suspected, circumstantially supported, never proven. Anyone who tells you they know for certain either way is overstating their evidence.

5. Why It Still Matters

Whether or not the TrueCrypt developers were specifically served with a gag order, the broader question the episode raises is real and unresolved:

The "honourable shutdown" framing

The way the popular reading frames the TrueCrypt story — "they were forced to backdoor or shut down, and they chose to shut down" — is morally satisfying and probably partly true. But it understates the cost. Whoever the TrueCrypt developers were, they:

• Lost a decade of work overnight
• Could not warn their users about what triggered the shutdown
• Could not name the party that pressured them
• Could not appeal publicly
• Could not even publish the keys to a successor project that would have been beyond the reach of the order

That is not a clean win. That is what a working secret-order regime looks like when it bumps into someone with principles: the project dies, the public narrative is controlled by the order's issuer, and the user community is left to guess. The "honourable option" framing is sentimentally true and structurally wrong — there should not be a situation in which a developer's choices are limited to "betray your users" or "destroy your work and never tell anyone why."

A society in which the people who build privacy tools can be ordered, in secret, to either undermine their own product or destroy it — and forbidden from telling anyone which — is not a society that has chosen privacy. It is a society that has chosen to permit the appearance of privacy while reserving the right to revoke it at any time, against any individual, with no accountability and no possibility of public oversight.

6. Bottom Line