From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Bug in cryptsetup?
Date: Sat, 19 Jun 2010 22:16:38 +0200 [thread overview]
Message-ID: <20100619201638.GA29635@fancy-poultry.org> (raw)
In-Reply-To: <20100619172056.EB09B655213@c-in3ws--03-02.sv2.lotusliveops.com>
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.
next prev parent reply other threads:[~2010-06-19 20:16 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 [this message]
2010-06-19 21:50 ` Milan Broz
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=20100619201638.GA29635@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=dm-crypt@saout.de \
/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