From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] migrate luks key-slots to another luks container
Date: Wed, 16 Jan 2013 21:33:49 +0100 [thread overview]
Message-ID: <50F70EAD.9080607@gmail.com> (raw)
In-Reply-To: <20130116201912.GC9508@tansi.org>
On 01/16/2013 09:19 PM, Arno Wagner wrote:
> Come to think of it, here is a very dirty way to do this:
> Have the people accessing this map the old container (header+
> keyslot area is enough, use, e.g. a loop file), then read the
> master key (see FAQ) and use that in a script to open your
> second (new) container.
And what to do if the master key is longer for the new container?
No, really, LUKS is a simple standard for a reason :)
The master key in keyslot is always encrypted with the same algorithm
as the data. cryptsetup-reencrypt requires entering all passphrases
or alternatively use only one (destroying others) and allow add them later.
Surely we can create some "hack" script, but then I would expect
people doing this exactly understand (not only security) consequences.
Milan
next prev parent reply other threads:[~2013-01-16 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 18:34 [dm-crypt] migrate luks key-slots to another luks container Alexander 'Leo' Bergolth
2013-01-16 18:50 ` .. ink ..
2013-01-16 19:57 ` Alexander 'Leo' Bergolth
2013-01-16 20:05 ` Milan Broz
2013-01-16 20:14 ` Arno Wagner
2013-01-16 20:19 ` Arno Wagner
2013-01-16 20:33 ` Milan Broz [this message]
2013-01-16 20:51 ` Alexander 'Leo' Bergolth
2013-01-16 21:08 ` Arno Wagner
2013-01-16 21:29 ` Alexander 'Leo' Bergolth
2013-01-16 21:54 ` Arno Wagner
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=50F70EAD.9080607@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox