From: Alexander 'Leo' Bergolth <leo@strike.wu.ac.at>
To: Arno Wagner <arno@wagner.name>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] migrate luks key-slots to another luks container
Date: Wed, 16 Jan 2013 21:51:36 +0100 [thread overview]
Message-ID: <50F712D8.801@strike.wu.ac.at> (raw)
In-Reply-To: <20130116201455.GB9508@tansi.org>
Am 16.01.2013 21:14, schrieb Arno Wagner:
> Any reason why you want to change the cipher? After all, you can
> not enlarge the key and keep the keyslots.
>
> As to size, just enlarge the partition. Offset, I don't know,
> but if you do not need to keep any data, just changing the
> repective fiels in the header should do it. But is there really
> any reason to change the offset?
The motivation behind this is because I'd like to migrate the data to
another system using a different raid layout.
To ensure correct data alignment with the new stripe size, I need to
change the payload-offset using --align-payload.
Besides, I'd like to change cipher from aes-cbc-essiv:sha256 to
aes-xts-plain. (Key size is 256 bit on both.)
The source system is currently mounted, so my plan is to create a new
luks container (preferrably using the same keyslots) and then just rsync
the data.
Cheers,
--leo
> On Wed, Jan 16, 2013 at 08:57:47PM +0100, Alexander 'Leo' Bergolth wrote:
>> Am 16.01.2013 19:50, schrieb .. ink ..:
>>> Is it possible to move the passphrases from one luks container to a new
>>> one with different cipher, size and payload offset? (There is currently
>>> no data on the new container, I just want to keep the old passphrases.)
>>>
>>> any reason why you dont want to just add those old passphrases to the
>>> new container using "luksAddKey"?
>>
>> I'd like to transfer the key-slots so that the same passphrases can
>> be used to unlock them.
>> I don't know the passphrases. (Just one of them.)
>>
>> Cheers,
>> --leo
>> --
>> e-mail ::: Leo.Bergolth (at) wu.ac.at
>> fax ::: +43-1-31336-906050
>> location ::: IT-Services | Vienna University of Economics | Austria
>>
>> _______________________________________________
>> dm-crypt mailing list
>> dm-crypt@saout.de
>> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
e-mail ::: Leo.Bergolth (at) wu.ac.at
fax ::: +43-1-31336-906050
location ::: IT-Services | Vienna University of Economics | Austria
next prev parent reply other threads:[~2013-01-16 20:51 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
2013-01-16 20:51 ` Alexander 'Leo' Bergolth [this message]
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=50F712D8.801@strike.wu.ac.at \
--to=leo@strike.wu.ac.at \
--cc=arno@wagner.name \
--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 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.