From: Alexander 'Leo' Bergolth <leo@strike.wu.ac.at>
To: dm-crypt@saout.de
Subject: [dm-crypt] migrate luks key-slots to another luks container
Date: Wed, 16 Jan 2013 19:34:38 +0100 [thread overview]
Message-ID: <50F6F2BE.9080203@strike.wu.ac.at> (raw)
Hi!
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.)
Do I need to transfer the master key and the key-slots or just the
key-slots?
Any hints?
Thanks,
--leo
--
e-mail ::: Leo.Bergolth (at) wu.ac.at
fax ::: +43-1-31336-906050
location ::: IT-Services | Vienna University of Economics | Austria
next reply other threads:[~2013-01-16 18:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 18:34 Alexander 'Leo' Bergolth [this message]
2013-01-16 18:50 ` [dm-crypt] migrate luks key-slots to another luks container .. 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
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=50F6F2BE.9080203@strike.wu.ac.at \
--to=leo@strike.wu.ac.at \
--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