From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <arno@wagner.name>
Received: from v1.tansi.org (mail.tansi.org [84.19.178.47])
 by mail.server123.net (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Sun, 29 Mar 2020 19:19:08 +0200 (CEST)
Received: from gatewagner.dyndns.org (81-6-44-245.init7.net [81.6.44.245])
 by v1.tansi.org (Postfix) with ESMTPA id 6D07D14013F
 for <dm-crypt@saout.de>; Sun, 29 Mar 2020 19:19:07 +0200 (CEST)
Date: Sun, 29 Mar 2020 19:19:08 +0200
From: Arno Wagner <arno@wagner.name>
Message-ID: <20200329171907.GA15950@tansi.org>
References: <r5oh6a$j18$1@ciao.gmane.io> <20200329102015.GA13364@tansi.org>
 <sAFa3HRnMo-fU86koyorBn0p9157R3nI1B8qZI-tEuE5CkfOoNo0vHpDfi64DWv_3bThmnL3GjnsqmPwcoIOtcZL_UzjIza7MJ_-94NYFYA=@protonmail.ch>
 <d36d15f1-72ea-5df3-041b-8aa20d9b9cf0@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d36d15f1-72ea-5df3-041b-8aa20d9b9cf0@gmail.com>
Subject: Re: [dm-crypt] Why is the chk_luks_keyslots tool not routinely
 included?
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <https://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <https://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <https://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: "dm-crypt@saout.de" <dm-crypt@saout.de>

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