From: "Michael Kjörling" <michael@kjorling.se>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS FAQ separate for LUKS1/LUKS2, or combined? Was: cryptsetup Yubikey challenge-response support
Date: Sun, 12 Apr 2020 13:00:40 +0000 [thread overview]
Message-ID: <9d06b2b9-96c5-45e7-8c1f-631e65db8bcd@localhost> (raw)
In-Reply-To: <20200411222340.GA26867@tansi.org>
On 12 Apr 2020 00:23 +0200, from arno@wagner.name (Arno Wagner):
> @everybody: What are the preferences: Separate LUKS 2 FAQ or
> section in the existing FAQ?
LUKS is LUKS. Most of the concepts are similar. Most of the problems
LUKS (1 and 2) solve are similar.
Yes, some _answers_ might well be different for LUKS 1 or LUKS 2. But
the _questions_ should be mostly the same, and _why_ to do one thing
or another should be similar. The only obvious exception to that which
I can think of is where something is _possible_ in LUKS 2, but simply
not possible in LUKS 1, _and_ that would be worthy of inclusion in a
FAQ in the first place.
There's already parts in the FAQ that discuss dm-crypt, RAM,
passphrases, erasing data, and so on; so there's ample precedent that
the FAQ already covers more than LUKS (1) proper.
Therefore, in the name of consistency and ease of reading, I would
suggest to keep it all in one document, _but_ clearly mark the parts
that only apply to one or the other. (This could be whole Q/A tuples,
or just a portion such as an example command line.) Also perhaps add
something near the top for how to tell based on an existing container,
ideally irrespective of how the distribution does things, whether a
LUKS container is LUKS 1 or LUKS 2.
--
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
next prev parent reply other threads:[~2020-04-12 13:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <233063842.2717340.1586366160963.ref@mail.yahoo.com>
2020-04-08 17:16 ` [dm-crypt] cryptsetup Yubikey challenge-response support JT Morée
2020-04-10 3:01 ` Dan Farrell
2020-04-11 14:49 ` JT Moree
2020-04-11 16:09 ` Milan Broz
2020-04-11 19:56 ` Arno Wagner
2020-04-11 21:05 ` JT Moree
2020-04-11 22:23 ` Arno Wagner
2020-04-12 13:00 ` Michael Kjörling [this message]
2020-04-14 10:56 ` [dm-crypt] LUKS FAQ separate for LUKS1/LUKS2, or combined? Was: " Milan Broz
2020-04-15 22:25 ` Arno Wagner
2020-04-14 11:35 ` [dm-crypt] " Milan Broz
2020-04-15 21:47 ` Arno Wagner
2020-04-15 6:37 ` Dan Farrell
2020-04-15 6:48 ` Dan Farrell
2020-04-15 7:08 ` Dan Farrell
2020-04-15 19:38 ` Milan Broz
2020-04-16 2:03 ` Dan Farrell
2020-04-16 10:36 ` 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=9d06b2b9-96c5-45e7-8c1f-631e65db8bcd@localhost \
--to=michael@kjorling.se \
--cc=dm-crypt@saout.de \
/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