From: Milan Broz <mbroz@redhat.com>
To: Si St <sigbj-st@operamail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Bug in cryptsetup?
Date: Sat, 19 Jun 2010 23:50:04 +0200 [thread overview]
Message-ID: <4C1D3B8C.9030803@redhat.com> (raw)
In-Reply-To: <20100619172056.EB09B655213@c-in3ws--03-02.sv2.lotusliveops.com>
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
next prev parent reply other threads:[~2010-06-19 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 17:20 [dm-crypt] Bug in cryptsetup? Si St
2010-06-19 20:16 ` Heinz Diehl
2010-06-19 21:50 ` Milan Broz [this message]
2010-06-19 22:13 ` Arno Wagner
2010-06-19 22:26 ` Christoph Anton Mitterer
2010-06-20 19:54 ` Arno Wagner
-- strict thread matches above, loose matches on Subject: below --
2010-06-20 12:54 Si St
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C1D3B8C.9030803@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=sigbj-st@operamail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox