From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 4IOVBmkYSLtY for ; Thu, 20 Jun 2013 12:04:01 +0200 (CEST) Received: from mout.web.de (mout.web.de [212.227.17.11]) by mail.saout.de (Postfix) with ESMTP for ; Thu, 20 Jun 2013 12:04:01 +0200 (CEST) Received: from [192.168.178.35] ([89.246.59.146]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0MgfTT-1Ud9Gx2ceV-00NzgC for ; Thu, 20 Jun 2013 12:04:00 +0200 Message-ID: <51C2D38C.5030203@web.de> Date: Thu, 20 Jun 2013 12:03:56 +0200 From: Jan Janssen MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [dm-crypt] Truecrypt system partition support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Hi, I just stumbled upon truecrypt support in cryptsetup. It sounds nice, but there is one big issue that prevents it from being useful in situations where the truecrypt partition is encrypted using system mode and other partitions on the drive are mounted/in use (such as dual boot on a single drive system). There is this small limitation that you have to specify the whole device for opening tcrypt system devices. And the fact that tcryptOpen refuses to open if that device is mapped/mounted already prevents me from using cryptsetup altogether for my truecrypt partition. It would be nice if this could be fixed/worked around with. Jan