From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <htd+ml@fritha.org>
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.13])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sun,  8 Feb 2015 13:02:38 +0100 (CET)
Received: from localhost ([88.90.246.181]) by mrelayeu.kundenserver.de
 (mreue103) with ESMTPSA (Nemesis) id 0Linfx-1XmCsV0brZ-00cupL for
 <dm-crypt@saout.de>; Sun, 08 Feb 2015 13:02:38 +0100
Date: Sun, 8 Feb 2015 13:02:36 +0100
From: Heinz Diehl <htd+ml@fritha.org>
Message-ID: <20150208120236.GA3878@fritha.org>
References: <mb7b8h$2m5$1@ger.gmane.org> <54D7347F.1080608@gmail.com>
 <mb7inu$gtm$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <mb7inu$gtm$1@ger.gmane.org>
Subject: Re: [dm-crypt] truecrypt - what's the real story behind it?
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 08.02.2015, U.Mutlu wrote: 

> Then I wonder if the NSA/CIA/DHS etc. was involved in the decision of the
> authors to abondon truecrypt developement, or was there maybe a mole among
> the devs?... conspiracy mode off  :-)

Nobody knows but the Truecrypt devs. IMHO the reasons to abandon TC development
was rather financial ones.
 
> The advantage of truecrypt, as I see it, is that it is a multiplatform
> solution; works even under the Windows cr*p

If you use Wind*ws as your platform, you'll most likely have a lot more serious
security problems than a simple "how reliable is TC"... ;-)