From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com
 [IPv6:2a00:1450:400c:c03::234])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sun,  8 Feb 2015 11:03:45 +0100 (CET)
Received: by mail-we0-f180.google.com with SMTP id m14so21419552wev.11
 for <dm-crypt@saout.de>; Sun, 08 Feb 2015 02:03:45 -0800 (PST)
Message-ID: <54D7347F.1080608@gmail.com>
Date: Sun, 08 Feb 2015 11:03:43 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <mb7b8h$2m5$1@ger.gmane.org>
In-Reply-To: <mb7b8h$2m5$1@ger.gmane.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
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: "U.Mutlu" <for-gmane@mutluit.com>, dm-crypt@saout.de

On 02/08/2015 10:45 AM, U.Mutlu wrote:
> Hi,
> the cryptsetup tool supports besides plain and luks, also loopaes and truecrypt.
> I now compiled truecrypt-7.1a, and it looks not bad.

Please see the https://ciphershed.org project which tries to continue with development.

> I wonder why some people say truecrypt is no more secure.
> Which part or method of truecrypt is allegedly broken? Can't be fixed?

There is no publicly known serious problem there. But there are license and other
non-technical problems. You will get more info on devel list of project above.

> And: is full truecrypt functionality integrated in cryptsetup tool? I mean the 
> create-options below.

There is full support for mapping existing containers (with some exceptions,
see man page).

There is intentionally no new container creation support in cryptsetup and
I am not planning to add it.
We will better invest time to improving LUKS.

You can use tcplay or older version of truecrypt for that (or ciphershed when
released).

Milan