All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Kozina <okozina@redhat.com>
To: dm-crypt@saout.de
Cc: Dominic Raferd <dominic@timedicer.co.uk>
Subject: Re: [dm-crypt] LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
Date: Wed, 29 May 2019 13:06:51 +0200	[thread overview]
Message-ID: <ff5dbe73-fe02-fb17-ef7a-9ab74441f2f0@redhat.com> (raw)
In-Reply-To: <CAF9Mo3L81nw5dSiwyKHrkDOdC8ONmh6VsphEFJTXdZazsM0LvA@mail.gmail.com>

On 5/29/19 11:56 AM, Dominic Raferd wrote:
> Thanks Guilhem, those links are very helpful but I have not solved it 
> yet. Another change in the new cryptsetup is LUKS2 and use of the kernel 
> keyring, so when run from a booted system dmcrypt_derived just returns a 
> message that the source crypt device uses the keyring - I don't know how 
> to obtain the actual key to use it in the creation of the second crypt 
> device (or maybe it is impossible

Not sure why you need to reuse volume key put in dm-crypt exactly but if 
you rely on the classical method, you may use --disable-keyring 
parameter of cryptsetup. With this parameter cryptsetup uploads the key 
in hexbyte representation as with LUKS1 format.

Regards
O.

  reply	other threads:[~2019-05-29 11:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 11:41 [dm-crypt] LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk Dominic Raferd
2019-05-22 12:46 ` Arno Wagner
2019-05-22 12:53   ` Dominic Raferd
2019-05-22 13:15     ` Arno Wagner
2019-05-22 17:16     ` Guilhem Moulin
2019-05-29  9:56       ` Dominic Raferd
2019-05-29 11:06         ` Ondrej Kozina [this message]
2019-05-29 11:26           ` Dominic Raferd
2019-05-29 13:43             ` Guilhem Moulin
2019-06-07  8:56               ` Dominic Raferd
2019-06-07 10:52                 ` Guilhem Moulin

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=ff5dbe73-fe02-fb17-ef7a-9ab74441f2f0@redhat.com \
    --to=okozina@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=dominic@timedicer.co.uk \
    /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.