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 YxoeN9f63SqL for ; Mon, 24 Jun 2013 07:49:46 +0200 (CEST) Received: from mail-ee0-x22c.google.com (mail-ee0-x22c.google.com [IPv6:2a00:1450:4013:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Mon, 24 Jun 2013 07:49:45 +0200 (CEST) Received: by mail-ee0-f44.google.com with SMTP id c13so5670448eek.17 for ; Sun, 23 Jun 2013 22:49:44 -0700 (PDT) Message-ID: <51C7DDBC.9080107@gmail.com> Date: Mon, 24 Jun 2013 07:48:44 +0200 From: Milan Broz MIME-Version: 1.0 References: <51C2D38C.5030203@web.de> <51C332C2.1000900@gmail.com> <1468118.MD1b3jT5q3@brinja> <51C71539.7020203@gmail.com> <51C76342.6070401@web.de> In-Reply-To: <51C76342.6070401@web.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Truecrypt system partition support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Janssen Cc: dm-crypt@saout.de On 23.6.2013 23:06, Jan Janssen wrote: > On 06/23/2013 05:33 PM, Milan Broz wrote: >> Hi, >> >> The shared device for system encryption is fixed in devel git >> http://code.google.com/p/cryptsetup/source/detail?r=a36de633d50d1e047cf5c0c3bc5e4d16a411fb62# >> >> Please let me know if there is any other problem. > > Still can't open it :( > > # sudo cryptsetup --tcrypt-system tcryptOpen /dev/sda windows > device-mapper: reload ioctl on failed: Invalid argument > > The journal has some additional information: > kernel: device-mapper: table: 254:1: crypt: Device lookup failed > kernel: device-mapper: ioctl: error adding target to table Hm, seems like completely different problem. I cannot check whats going on without more information here, ideally - cryptsetup output with --debug switch - tcryptDump (mainly offsets and data sizes stored there) - exact sizes of partitions (fdils -l -u, blockdev --getsz /dev/sda* or so) (but please note it will provide some info which is hidden, do not send it if it is problem :-) Ideally I would like to reproduce it, for my encrypted VM on partition it works. How did you create this config? ANy manipulations with apartitions after system reencryption? > > Also, something's off about the --key-file option with tcrypt. I can't > get it to accept my password from the file. But if I pipe it with cat > to stdin it works. Maybe it's supposed to be this way, but then I think > it needs extra mention in the manpage. And maybe there should be a way > to provide a --passphrase-file option or something along those lines > if the current handling is different to how its handled for luks. So you are not using Truecrypt keyfile but just passphrase in file, so pipe is the correct way. I thought it is explained in man page but if not, it need some care. If you have some idea how to describe it betrer, just send me a patch. (And adding more otpion will cause even more chaos here :) Thanks, Milan