From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] migrate luks key-slots to another luks container
Date: Wed, 16 Jan 2013 21:14:55 +0100 [thread overview]
Message-ID: <20130116201455.GB9508@tansi.org> (raw)
In-Reply-To: <50F7063B.9090607@strike.wu.ac.at>
Hmm.
I don't think that is possible at the moment. The experimental
"cryptsetup-reencrypt" requires all passphrases that should remain
active.
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?
Arno
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
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2013-01-16 20:14 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 [this message]
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=20130116201455.GB9508@tansi.org \
--to=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.