From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup Yubikey challenge-response support
Date: Sat, 11 Apr 2020 21:56:12 +0200 [thread overview]
Message-ID: <20200411195611.GA25259@tansi.org> (raw)
In-Reply-To: <6114e747-a8cd-c0c6-ccc8-7f666f04d32b@gmail.com>
On Sat, Apr 11, 2020 at 18:09:46 CEST, Milan Broz wrote:
> On 11/04/2020 16:49, JT Moree wrote:
> > Arno is working on updating the docs for new features of luks2.
>
> Arno did not add anything to FAQ in this regard for the last two+ years (the last
> contribution was in 2017, I do not count last week change for "LUKS2 is not
> covered" FAQ commit.
> The FAQ is really obsolete now, and we have to update it or remove it
> from distribution soon.
> (Many people already complained through various channels.)
Well, many people complained and exactly zero did any work
or offered any work. Also, zero did complain to me (except
for the comments on the list here). These two details make
me very unconcerned about their complaints.
This is, at the moment, the LUKS 1 FAQ (and that was really
what the commit from last week was about), and as that it does
not need removing. It also covers quite a bit of stuff that is
not LUKS 1 specific and some stuff that is not even LUKS specific.
So unless you are positive nobody uses LUKS 1 anymore, and the
not LUKS 1 specific stuff is irrelevant, removing it would really
be the wrong approach.
If you want to start a LUKS 2 FAQ, be my guest. But be aware
that such a thing is a _lot_ of work before it is anywhere
near completion. That you do not have complete design
documentation for LUKS 2 (as far as I can tell) makes it
even harder. Maybe you write that documentation and as soon
as it is complete, I will go into the FAQ and start updating.
Regards,
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2020-04-11 19:56 UTC|newest]
Thread overview: 23+ 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 [this message]
2020-04-11 21:05 ` JT Moree
2020-04-11 22:23 ` Arno Wagner
2020-04-12 13:00 ` [dm-crypt] LUKS FAQ separate for LUKS1/LUKS2, or combined? Was: " Michael Kjörling
2020-04-14 10:56 ` 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
2020-04-08 8:37 7heo
2020-04-08 10:07 ` Nikolay Kichukov
2020-04-08 16:31 ` Tim Steiner
2020-04-08 22:18 ` Dan Farrell
-- strict thread matches above, loose matches on Subject: below --
2020-04-08 7:54 Dan Farrell
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=20200411195611.GA25259@tansi.org \
--to=arno@wagner.name \
--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