Return-Path: Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Mon, 12 Oct 2009 19:50:03 +0200 (CEST) Received: from list by lo.gmane.org with local (Exim 4.50) id 1MxP22-00031T-60 for dm-crypt@saout.de; Mon, 12 Oct 2009 19:50:02 +0200 Received: from 88.211.33.26 ([88.211.33.26]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Oct 2009 19:50:02 +0200 Received: from david by 88.211.33.26 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Oct 2009 19:50:02 +0200 From: David Greaves Date: Mon, 12 Oct 2009 11:58:10 +0000 (UTC) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: news Subject: [dm-crypt] Naming key slots to permit luksKillSlot to be aimed... List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de So I have multiple keyslots in use: * 1 for admin * 1 for userA * 1 for userB userA leaves without divulging passphrase; userB is out of reach. How do I know which slot to luksKillSlot? Have I missed something? A solution may be an optional name that shows up in luksDump and is setup at creation time: cryptsetup luksAddKey --name "admin" /dev/sda1 cryptsetup luksAddKey --name "johndoe" /dev/sda1 cheers David