From: Guilhem Moulin <guilhem@fripost.org>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Debian installer formatting LUKS2 devices by default?
Date: Tue, 31 Jul 2018 04:47:18 +0800 [thread overview]
Message-ID: <20180730204718.GA16752@localhost.localdomain> (raw)
In-Reply-To: <d349eeb9-4509-e188-4bb2-90854bcc9a69@gmail.com>
Hi Milan,
On Mon, 30 Jul 2018 at 12:51:11 +0200, Milan Broz wrote:
> We already added configure switch for default format, so now it is up
> to the distro maintainer.
Right, but Debian is quite conservative in that regard, hence I
preferred to asked you to clarify your future plans ;-)
> I would like to change upstream default in some next version (see below),
> but we still have some issues to solve.
> […]
Thank you very much for the explanation and the very detailed roadmap!
> The major LUKS2 fix is that libcryptsetup is now linked to libblkid
> and will not automatically recover from secondary header if it detects
> another (fs) signature.
> (Because recovery could revert intentional change... We were too aggressive here.)
> Libblkid is already used in dm/udev rules, so it should not increase
> any image sizes. (And it can be disabled in configure if needed.)
I guess to you mean 8bee1a2? I hope 2.33 will be released upstream and
uploaded to Debian before the freeze.
Cheers,
--
Guilhem.
next prev parent reply other threads:[~2018-07-30 20:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 8:16 [dm-crypt] Debian installer formatting LUKS2 devices by default? Guilhem Moulin
2018-07-30 10:51 ` Milan Broz
2018-07-30 20:47 ` Guilhem Moulin [this message]
2018-07-31 6:00 ` Michael Kjörling
2018-07-31 7:53 ` Guilhem Moulin
2018-11-23 9:21 ` Milan Broz
2018-11-23 18:26 ` Guilhem Moulin
2018-11-23 18:46 ` Milan Broz
2019-01-25 13:54 ` Guilhem Moulin
2019-01-25 14:31 ` Milan Broz
2019-01-25 15:05 ` Guilhem Moulin
2019-02-05 15:29 ` Milan Broz
2018-07-31 8:56 ` Milan Broz
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=20180730204718.GA16752@localhost.localdomain \
--to=guilhem@fripost.org \
--cc=dm-crypt@saout.de \
--cc=gmazyland@gmail.com \
/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.