<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div><div></div><div>Me too. It really does make you wonder what hidden factors might have been at work. </div><div><br></div><div><br></div><div>wg<div>---<div><div>www.pelicancrossing.net</div><div>Twitter: @wendyg</div></div></div></div></div><br><br><br>-------- Original message --------<br>From: bakeryworms@gmail.com <br>Date: 2014/05/30 14:55 (GMT+00:00) <br>To: ukcrypto@chiark.greenend.org.uk,UK Cryptography Policy Discussion Group <ukcrypto@chiark.greenend.org.uk> <br>Subject: Re: TrueCrypt takedown <br> <br><br>It made me think of the Lavabit shutdown. <br><br>KRS<br>Mark<br><br> Original Message <br>From: JJ Gray<br>Sent: Friday, 30 May 2014 14:43<br>To: UK Cryptography Policy Discussion Group<br>Reply To: UK Cryptography Policy Discussion Group<br>Subject: Re: TrueCrypt takedown<br><br>On 30/05/2014 10:44, Graham Cobb wrote:<br><br>> of any issues). If the developers have stopped work on TrueCrypt then<br>> that seems a reasonable warning to leave behind to the world.<br>> <br>> That does seem the simplest explanation to me.<br><br>That would appear to be the case, at least at this stage.<br>https://gist.github.com/ValdikSS/c13a82ca4a2d8b7e87ff<br><br>Cheers,<br>JJ<br><br><br><br><br><br></body>