From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <medhefgo@web.de>
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 WmsJ1MDJjxqZ for <dm-crypt@saout.de>;
 Mon,  1 Jul 2013 12:33:53 +0200 (CEST)
Received: from mout.web.de (mout.web.de [212.227.17.12])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Mon,  1 Jul 2013 12:33:53 +0200 (CEST)
Received: from [192.168.178.35] ([89.246.61.102]) by smtp.web.de (mrweb002)
 with ESMTPSA (Nemesis) id 0MDxSJ-1V1aSE0MBz-00HNay for <dm-crypt@saout.de>;
 Mon, 01 Jul 2013 12:33:53 +0200
Message-ID: <51D15B0F.6080201@web.de>
Date: Mon, 01 Jul 2013 12:33:51 +0200
From: Jan Janssen <medhefgo@web.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [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

Hi,

while testing how the tcrypt passphrase + keyfile logic works, I
realized that there doesn't seem to be a way to protect the hidden
volume from being damaged by writes to a mounted outer volume like
truecrypt does. I think this deserves a warning in the man page
since this is a potential data loss.

Thanks,
Jan