From: Jan Janssen <medhefgo@web.de>
Date: Fri, 21 Jun 2013 15:58:58 +0200
Message-ID: <1468118.MD1b3jT5q3@brinja>
In-Reply-To: <51C332C2.1000900@gmail.com>
References: <51C2D38C.5030203@web.de> <51C332C2.1000900@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Subject: Re: [dm-crypt] Truecrypt system partition support
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de

On Thursday 20 June 2013 18:50:10 Milan Broz wrote:
> Hi,
>=20
> well, you are probably the first real user I know about who tried sys=
tem
> encryption truecrypt mapping :) So it is quite possible there are som=
e
> problems.

That's probably because it's not well advertised. I found out about it =
by
accident and wanted to give it a try.

> Please can you describe exactly you configuration (I think I understa=
nd the
> problem but exact description could be better.)
> Why is main device used? Mapped/mounted other partition or something =
else?
> Should be easy to fix I think (we have already --shared option for pl=
ain
> mode).
>=20
> (If you are able to map it with normal truecrypt in Linux, output of =
lsblk
> with encryption mapping active should be enough for me.)
>=20
> Thanks,
> Milan

It's a simple single drive layout with a boot, windows and arch patitio=
n:
NAME           FSTYPE      LABEL   UUID                                =
 MOUNTPOINT
sda                                                                    =
=20
=E2=94=9C=E2=94=80sda1         ext4        Boot    bdf8d95e-3a5a-4944-a=
ff1-5ce8107ee679 /boot
=E2=94=9C=E2=94=80sda2                                                 =
                =20
=E2=94=82 =E2=94=94=E2=94=80truecrypt1 ntfs        Windows 72682F78682F=
39ED                     /mnt/windows
=E2=94=94=E2=94=80sda3         crypto_LUKS         d998f50f-c40b-4d53-b=
683-90bd30da1272=20
  =E2=94=94=E2=94=80system     ext4        Arch    52b8c62b-23df-4b07-8=
75b-16da3cb0cb91 /

Also, it took me a while to figure out (thanks to the manpage) that you=
 have
to use /dev/sda to open in system mode. It would be useful if cryptsetu=
p
could either figure out where to look for its offset from /dev/sda2 lik=
e
the "real" truecrypt does or at least give a hint that in system mode t=
he
drive should be used instead of the partition. Or maybe give the drive
to the system option like this:
    sudo cryptsetup --tcrypt-system=3D/dev/sda tcryptDump /dev/sda2

Jan