From: Arno Wagner <arno@wagner.name>
To: "dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Why is the chk_luks_keyslots tool not routinely included?
Date: Sun, 29 Mar 2020 19:19:08 +0200 [thread overview]
Message-ID: <20200329171907.GA15950@tansi.org> (raw)
In-Reply-To: <d36d15f1-72ea-5df3-041b-8aa20d9b9cf0@gmail.com>
On Sun, Mar 29, 2020 at 16:09:56 CEST, Milan Broz wrote:
> On 29/03/2020 14:34, Jordan Glover wrote:
> > On Sunday, March 29, 2020 10:20 AM, Arno Wagner <arno@wagner.name> wrote:
> >
> >> I think that is a decision by the distros. I am certainly
> >> willing to maintain it for the foreseeable future. It is
> >> not really much effort.
> >
> > The distros just do "make install" [1]. I think it's upstream who decides what this command does.
> >
> > [1] https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/cryptsetup#n39
>
> My plan was to include this check in repair command instead of adding
> additional binary. (The code could remain basically the same.)
>
> With LUKS2 we can store other data in binary keyslot area (depends on
> type), so it need a little bit more work but it should not be a big
> problem.
>
> Please report an issue for it, that helps to not forget about it.
>
> Thanks,
> Milan
Perfecly fine by me, feel fre to re-use any of the code that
is there as you see fit.
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-29 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 21:56 [dm-crypt] Why is the chk_luks_keyslots tool not routinely included? Robert Nichols
2020-03-29 10:20 ` Arno Wagner
2020-03-29 12:34 ` Jordan Glover
2020-03-29 14:09 ` Milan Broz
2020-03-29 17:19 ` Arno Wagner [this message]
2020-03-30 0:44 ` Robert Nichols
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=20200329171907.GA15950@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