From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound3-nonen.messaging.lotuslive.com (outbound3-nonen.messaging.lotuslive.com [8.12.152.100]) by mail.saout.de (Postfix) with ESMTP for ; Sat, 19 Jun 2010 19:20:58 +0200 (CEST) Received: from outbound3.messaging.lotuslive.com (49.33.5.10.in-addr.arpa [10.5.33.49]) by c-in3obnd03-01.sv2.lotusliveops.com (Postfix) with ESMTP id 1130A4A493C for ; Sat, 19 Jun 2010 17:20:57 +0000 (GMT) Received: from c-in3ofil03-01.sv2.lotusliveops.com (54.33.6.10.in-addr.arpa [10.6.33.54]) by c-in3obnd03-01.sv2.lotusliveops.com (Postfix) with ESMTP id 0DE244A4932 for ; Sat, 19 Jun 2010 17:20:57 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 From: "Si St" Date: Sat, 19 Jun 2010 18:20:56 +0100 Message-Id: <20100619172056.EB09B655213@c-in3ws--03-02.sv2.lotusliveops.com> Subject: [dm-crypt] Bug in cryptsetup? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de --cryptsetup version 1.0.3 , OS =3D SLED_10_SP3-- Upon this command: cryptsetup luksDelKey 1 /dev/hda5 I receive this message: WARNING! =3D=3D=3D=3D=3D=3D=3D=3D This is the last keyslot. Device will become unusable after purging this ke= y. Are you sure? (Type uppercase yes): But upon this command: cryptsetup luksDelKey /dev/hda5 1 I receive only that I succeeded, and the actual Key in Slot 1 is disabled t= esting it with luksDump. Of course I did not dare to proceed after the frightening message in the fi= rst place and exited with Ctrl-C. Is there a bug here or is it just like the message explains. In this instan= ce it is easy to mistake by putting the keyslot number in the front and pro= ceed thinking that everything is okey. Any good explanation here? SS-NORWAY --=20 _______________________________________________ Surf the Web in a faster, safer and easier way: Download Opera 9 at http://www.opera.com