From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com
 [IPv6:2a00:1450:4864:20::441])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sun, 29 Mar 2020 16:09:59 +0200 (CEST)
Received: by mail-wr1-x441.google.com with SMTP id s1so17746720wrv.5
 for <dm-crypt@saout.de>; Sun, 29 Mar 2020 07:09:59 -0700 (PDT)
References: <r5oh6a$j18$1@ciao.gmane.io> <20200329102015.GA13364@tansi.org>
 <sAFa3HRnMo-fU86koyorBn0p9157R3nI1B8qZI-tEuE5CkfOoNo0vHpDfi64DWv_3bThmnL3GjnsqmPwcoIOtcZL_UzjIza7MJ_-94NYFYA=@protonmail.ch>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <d36d15f1-72ea-5df3-041b-8aa20d9b9cf0@gmail.com>
Date: Sun, 29 Mar 2020 16:09:56 +0200
MIME-Version: 1.0
In-Reply-To: <sAFa3HRnMo-fU86koyorBn0p9157R3nI1B8qZI-tEuE5CkfOoNo0vHpDfi64DWv_3bThmnL3GjnsqmPwcoIOtcZL_UzjIza7MJ_-94NYFYA=@protonmail.ch>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
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: Jordan Glover <Golden_Miller83@protonmail.ch>, Arno Wagner <arno@wagner.name>
Cc: "dm-crypt@saout.de" <dm-crypt@saout.de>

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