From: Milan Broz <gmazyland@gmail.com>
To: Jan Janssen <medhefgo@web.de>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Truecrypt system partition support
Date: Thu, 20 Jun 2013 18:50:10 +0200 [thread overview]
Message-ID: <51C332C2.1000900@gmail.com> (raw)
In-Reply-To: <51C2D38C.5030203@web.de>
On 06/20/2013 12:03 PM, Jan Janssen wrote:
> 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.
Hi,
well, you are probably the first real user I know about who tried system encryption
truecrypt mapping :) So it is quite possible there are some problems.
Please can you describe exactly you configuration (I think I understand 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 plain mode).
(If you are able to map it with normal truecrypt in Linux, output of lsblk
with encryption mapping active should be enough for me.)
Thanks,
Milan
next prev parent reply other threads:[~2013-06-20 16:50 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 [this message]
2013-06-21 13:58 ` Jan Janssen
2013-06-23 15:33 ` Milan Broz
2013-06-23 21:06 ` Jan Janssen
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=51C332C2.1000900@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=medhefgo@web.de \
/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.