From: Guilhem Moulin <guilhem@fripost.org>
To: Dominic Raferd <dominic@timedicer.co.uk>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
Date: Wed, 22 May 2019 19:16:15 +0200 [thread overview]
Message-ID: <20190522171614.GA23632@fripost.org> (raw)
In-Reply-To: <CAF9Mo3JhQ1AQ5-0a4o_EYou5mOGzW1VZEOC7mYqmVVUMGBiqcQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Hi Dominic,
On Wed, 22 May 2019 at 13:53:07 +0100, Dominic Raferd wrote:
> Thanks Arno, I think it is Debian really (rather than Ubuntu), but I
> couldn't see where to ask except here. Will dig some more.
For Debian you could file a bug against the ‘cryptsetup-initramfs’
package, see https://tracker.debian.org/pkg/cryptsetup and
https://www.debian.org/Bugs/ .
(‘Severity: wishlist’ I guess; at least your custom patch not applying
anymore isn't hinting at a regression.)
Also FWIW we (Debian packaging team) have native support for unlocking
multiple devices at early boot stage with a single passphrase prompt,
see /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz and
/usr/share/doc/cryptsetup-run/README.* . If that doesn't cover your
workflow then please visit the above links and file a wishlist bug :-)
Cheers,
--
Guilhem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-05-22 17:23 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 [this message]
2019-05-29 9:56 ` Dominic Raferd
2019-05-29 11:06 ` Ondrej Kozina
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=20190522171614.GA23632@fripost.org \
--to=guilhem@fripost.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox