From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] unbound keys
Date: Tue, 31 Mar 2020 11:21:43 +0200 [thread overview]
Message-ID: <20200331092143.GA6454@tansi.org> (raw)
In-Reply-To: <8e692b82-04cc-693c-08e7-cb6524916c23@redhat.com>
On Tue, Mar 31, 2020 at 10:49:41 CEST, Ondrej Kozina wrote:
> Hi,
>
> On 3/30/20 10:17 PM, JT Morée wrote:
> >After reading the luks2 FAQ, spec and archives I don't understand what an unbound key is used for.
>
> That's our never ending struggle to improve documentation and blog posts
> coverage. Hope things get calmer after 2.4.0 release so that we can focus on
> this effort.
There is also the thing that the FAQ is LUKS1, not LUKS2.
As LUKS1 is still widely in use, it would not be a good
idea to take it down, buit ther is potential for confusion.
I have made it even clearer now in the Wiki that it is not
the LUKS2 FAQ. That does not exist at the moment.
I expect that at some time it will be a good idea to make
it dual-version with a marker of "LUKS", "LUKS2" or "LUKS+LUKS2"
for each entry, but I think LUKS2 is still too fluid for that
at the moment.
Will existing features be stable after 2.4.0 or do you plan
additional changes?
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-03-31 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5602805.1319309.1585599459612.ref@mail.yahoo.com>
2020-03-30 20:17 ` [dm-crypt] unbound keys JT Morée
2020-03-31 8:49 ` Ondrej Kozina
2020-03-31 9:21 ` Arno Wagner [this message]
2020-04-02 11:28 ` Ondrej Kozina
2020-04-02 17:58 ` Arno Wagner
2020-03-31 10:03 ` Ondrej Kozina
2020-03-31 15:05 ` JT Morée
2020-04-02 11:37 ` Ondrej Kozina
2020-04-03 20:53 ` JT Morée
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=20200331092143.GA6454@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