From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <htd@fancy-poultry.org>
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.186]) by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Sat, 19 Jun 2010 22:16:32 +0200 (CEST)
Date: Sat, 19 Jun 2010 22:16:38 +0200
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20100619201638.GA29635@fancy-poultry.org>
References: <20100619172056.EB09B655213@c-in3ws--03-02.sv2.lotusliveops.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100619172056.EB09B655213@c-in3ws--03-02.sv2.lotusliveops.com>
Subject: Re: [dm-crypt] Bug in cryptsetup?
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://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: <http://www.saout.de/mailman/listinfo/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 19.06.2010, Si St wrote: 

> Upon this command:
> cryptsetup luksDelKey 1 /dev/hda5
> I receive this message:
> 
> WARNING!
> ========
> 
> This is the last keyslot. Device will become unusable after purging this key.


I consider this a bug. The manpage says:

 luksKillSlot <device> <key slot number>
 wipe key with number <key slot> from LUKS device. A
 remaining passphrase or key file (via --key-file) must be supplied.

 luksDelKey <device> <key slot number>
 identical to luksKillSlot, but deprecated action name.

I think cryptsetup should have bailed out and exited,
because "1" is not a device.