public inbox for dm-crypt@saout.de
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Why is the chk_luks_keyslots tool not routinely included?
Date: Sun, 29 Mar 2020 12:20:15 +0200	[thread overview]
Message-ID: <20200329102015.GA13364@tansi.org> (raw)
In-Reply-To: <r5oh6a$j18$1@ciao.gmane.io>

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.

Regards,
Arno


On Sat, Mar 28, 2020 at 22:56:25 CET, Robert Nichols wrote:
> What is the rationale behind the chk_luks_keyslots tool not being included
> by default in cryptsetup packages?  It gets tiresome, and a bit
> embarrassing, explaining to novices who are in trouble that they need to
> build this tool from source.
> 
> -- 
> Bob Nichols     "NOSPAM" is really part of my email address.
>                 Do NOT delete it.
> 
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> https://www.saout.de/mailman/listinfo/dm-crypt

-- 
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

  reply	other threads:[~2020-03-29 10:30 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 [this message]
2020-03-29 12:34   ` Jordan Glover
2020-03-29 14:09     ` Milan Broz
2020-03-29 17:19       ` Arno Wagner
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=20200329102015.GA13364@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