From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Sat, 19 Jun 2010 23:50:08 +0200 (CEST)
Message-ID: <4C1D3B8C.9030803@redhat.com>
Date: Sat, 19 Jun 2010 23:50:04 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <20100619172056.EB09B655213@c-in3ws--03-02.sv2.lotusliveops.com>
In-Reply-To: <20100619172056.EB09B655213@c-in3ws--03-02.sv2.lotusliveops.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Si St <sigbj-st@operamail.com>
Cc: dm-crypt@saout.de

On 06/19/2010 07:20 PM, Si St wrote:
> --cryptsetup version 1.0.3 , OS = SLED_10_SP3--

Quite old version, it works for me in 1.1.2

> cryptsetup luksDelKey /dev/hda5 1
> 
> I receive only that I succeeded, and the actual Key in Slot 1 is disabled testing it with luksDump.

# cryptsetup luksDelKey 0 /dev/sde
luksDelKey is a deprecated action name.
Please use luksKillSlot.
Device 0 doesn't exist or access denied.

# cryptsetup luksDelKey /dev/sde 0
luksDelKey is a deprecated action name.
Please use luksKillSlot.

WARNING!
========
This is the last keyslot. Device will become unusable after purging this key.
...

# cryptsetup luksKillSlot /dev/sde 1
Key 1 not active. Can't wipe.

# cryptsetup --version            
cryptsetup 1.1.2


Can you reproduce it with recent version?
And I think we already found more problems with SLED10.

Milan