All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Alexander 'Leo' Bergolth <leo@strike.wu.ac.at>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] migrate luks key-slots to another luks container
Date: Wed, 16 Jan 2013 21:05:45 +0100	[thread overview]
Message-ID: <50F70819.6010308@gmail.com> (raw)
In-Reply-To: <50F7063B.9090607@strike.wu.ac.at>

On 01/16/2013 08:57 PM, 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.)

Then it is impossible (if you want to change encryption parameters
and master key).

New master key must be encrypted with the new algorithm and you cannot
do this for keyslots without passphrase knowledge for these keyslots.

Milan

  reply	other threads:[~2013-01-16 20:05 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 [this message]
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=50F70819.6010308@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=leo@strike.wu.ac.at \
    /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.