From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane-mx.org>
Received: from ciao.gmane.io (ciao.gmane.io [159.69.161.202])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange ECDHE (P-256) 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>; Sat, 28 Mar 2020 23:01:34 +0100 (CET)
Received: from list by ciao.gmane.io with local (Exim 4.92)
 (envelope-from <glkdd-dm-crypt@m.gmane-mx.org>) id 1jIJRQ-0005CO-36
 for dm-crypt@saout.de; Sat, 28 Mar 2020 22:56:32 +0100
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
Date: Sat, 28 Mar 2020 16:56:25 -0500
Message-ID: <r5oh6a$j18$1@ciao.gmane.io>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Subject: [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

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.