From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 29 May 2014 04:46:34 +0200 (CEST)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1WpqMU-0003mN-9n
 for dm-crypt@saout.de; Thu, 29 May 2014 04:46:34 +0200
Received: from c-24-14-20-249.hsd1.il.comcast.net ([24.14.20.249])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Thu, 29 May 2014 04:46:34 +0200
Received: from rnicholsNOSPAM by c-24-14-20-249.hsd1.il.comcast.net with local
 (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Thu, 29 May 2014 04:46:34 +0200
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
Date: Wed, 28 May 2014 21:46:19 -0500
Message-ID: <lm671s$tfp$1@ger.gmane.org>
References: <lm5p4u$mpl$1@ger.gmane.org>
 <1055768232.20140529110710@CryptoPhoto.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <1055768232.20140529110710@CryptoPhoto.com>
Subject: Re: [dm-crypt] TrueCrypt support ended -- "Not secure"
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 05/28/2014 08:07 PM, Chris Drake wrote:
> Hi Robert,
>
> That's a hoax - their domain got hijacked.
>
> Kind Regards,
> Chris Drake
>
>
> Thursday, May 29, 2014, 8:49:01 AM, you wrote:
>
> RN> Sourceforge page warns against continued use, and the latest release does not
> RN> permit creation of new volumes.
>
> RN> http://arstechnica.com/security/2014/05/truecrypt-is-not-secure-official-sourceforge-page-abruptly-warns/
>
> RN> http://truecrypt.sourceforge.net/
>
>
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>

It has been reported that the "hacked" release was certified with the
official TruCrypt signing key, and compromise of that key would be
even more damning.  Would someone who had gained access to that key
squander that power on a prank?

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.