From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 9a-5YU4ftgY2 for <dm-crypt@saout.de>;
 Tue,  2 Jul 2013 07:31:03 +0200 (CEST)
Received: from mail-ea0-x232.google.com (mail-ea0-x232.google.com
 [IPv6:2a00:1450:4013:c01::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Tue,  2 Jul 2013 07:31:03 +0200 (CEST)
Received: by mail-ea0-f178.google.com with SMTP id l15so2448931eak.37
 for <dm-crypt@saout.de>; Mon, 01 Jul 2013 22:31:02 -0700 (PDT)
Received: from [192.168.2.24] (56.157.broadband5.iol.cz. [88.100.157.56])
 by mx.google.com with ESMTPSA id w43sm34176146eez.6.2013.07.01.22.31.01
 for <dm-crypt@saout.de>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Mon, 01 Jul 2013 22:31:01 -0700 (PDT)
Message-ID: <51D26553.50808@gmail.com>
Date: Tue, 02 Jul 2013 07:29:55 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <51D15B0F.6080201@web.de> <51D1D5AF.9060502@gmail.com>
 <20130702010538.GA18826@tansi.org> <20130702012556.GB18826@tansi.org>
In-Reply-To: <20130702012556.GB18826@tansi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Tcrypt hidden volume
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 2.7.2013 3:25, Arno Wagner wrote:
> I just saw that there is a way in TrueCrypt to protect
> the hiden volume:
> http://www.truecrypt.org/docs/hidden-volume-protection
>
> Not that this is really better, as it will leave filesystem
> annomalies and possible error messages that indicate the
> presence of a hidden volume.

I think you cannot use hidden protection for other filesystem
(outer) than VFAT reliably (e.g. superblock backups are in hidden
disk area).

Cryptsetup TCRYPT support was meant to provide tool to be able
to fully access data on TrueCrypt volume, with source code under
clear common licence (GPL/LGPL).
I do not think we should provide every feature they provides
- if you need that, just install and use Truecrypt.

Milan