From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from srve.com (srve.com [208.69.183.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Thu, 29 May 2014 05:39:08 +0200 (CEST) Date: Thu, 29 May 2014 13:38:48 +1000 From: Chris Drake Message-ID: <463573419.20140529133848@CryptoPhoto.com> In-Reply-To: References: <1055768232.20140529110710@CryptoPhoto.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] TrueCrypt support ended -- "Not secure" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Hi Robert, It's not the *original* key apparently, but the new one for the current release. Current rumors are that they're committing suicide for the same reasons as Lavabit - which would explain why they're pushing people over to products with NSA key escrow built in. Kind Regards, Chris Drake Thursday, May 29, 2014, 12:46:19 PM, you wrote: RN> 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 >> RN> It has been reported that the "hacked" release was certified with the RN> official TruCrypt signing key, and compromise of that key would be RN> even more damning. Would someone who had gained access to that key RN> squander that power on a prank?