TrueCrypt takedown

Graham Cobb g+ukcrypto at
Fri May 30 10:44:57 BST 2014

On 30/05/14 02:55, dw+ukcrypto at wrote:
> On Fri, May 30, 2014 at 02:20:39AM +0100, Peter Fairbrother wrote:
>> No reasons why the code is/may be broken are given. Actually the "WARNING:
>> Using TrueCrypt is not secure as it may contain unfixed security issues"
>> does not even actually say TrueCrypt is broken, just that it may be.
> A little too obvious, but perhaps it's ...
...snip suggested issues...

Is my naive reading of the message unreasonable?  I read the message as
intended to remain up for a long time and just as a warning that as
there had been no further maintenance, there may have been issues found
since the last release which no one has fixed (not suggesting they know
of any issues).  If the developers have stopped work on TrueCrypt then
that seems a reasonable warning to leave behind to the world.

That does seem the simplest explanation to me.

At this stage, the more interesting question seems to be whether someone
will create a commercial or open-source follow-on.

More information about the ukcrypto mailing list