From: Guilhem Moulin <guilhem@fripost.org>
To: "Michael Kjörling" <michael@kjorling.se>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Debian installer formatting LUKS2 devices by default?
Date: Tue, 31 Jul 2018 15:53:42 +0800 [thread overview]
Message-ID: <20180731075342.GA25101@localhost.localdomain> (raw)
In-Reply-To: <20180731060030.GA15852@h-174-65.A328.priv.bahnhof.se>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
On Tue, 31 Jul 2018 at 06:00:30 +0000, Michael Kjörling wrote:
> Obviously, there's nothing stopping whoever is installing the system
> from dropping to a shell and setting up a container themselves, _even
> if_ the installer _only_ does one version of on-disk format for LUKS.
> So even if the installer _only_ does LUKS1, and the tools are built
> with LUKS1 as default, it's not like that will _prevent_ people from
> using the LUKS2 format if they really want to.
Sure, but now we can tell people wanting the installer to default to
LUKS2 that it'll be the new upstream default in the future, and also
give a rough ETA. It's more efficient at appeasing them than replying
they need to drop to a shell and manually format & unlock the volume :-)
--
Guilhem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-07-31 7:53 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
2018-07-31 6:00 ` Michael Kjörling
2018-07-31 7:53 ` Guilhem Moulin [this message]
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=20180731075342.GA25101@localhost.localdomain \
--to=guilhem@fripost.org \
--cc=dm-crypt@saout.de \
--cc=michael@kjorling.se \
/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.