All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Janssen <medhefgo@web.de>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Truecrypt system partition support
Date: Sun, 23 Jun 2013 23:06:10 +0200	[thread overview]
Message-ID: <51C76342.6070401@web.de> (raw)
In-Reply-To: <51C71539.7020203@gmail.com>

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

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.

Thanks
Jan

  reply	other threads:[~2013-06-23 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 10:03 [dm-crypt] Truecrypt system partition support Jan Janssen
2013-06-20 16:50 ` Milan Broz
2013-06-21 13:58   ` Jan Janssen
2013-06-23 15:33     ` Milan Broz
2013-06-23 21:06       ` Jan Janssen [this message]
2013-06-24  5:48         ` Milan Broz
2013-06-24 13:55           ` Jan Janssen
2013-06-30  9:11             ` Milan Broz
2013-06-30 11:44               ` Jan Janssen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51C76342.6070401@web.de \
    --to=medhefgo@web.de \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.