[pkg-cryptsetup-devel] Bug#570312: Bug#570312: cryptsetup: luksKillSlot reports incorrect slot unlocked

[Jonas Meurer]

hey alex,

On 17/02/2010 Alex Roper wrote:
> When you use luksKillSlot to kill key slot X, and then enter the
> passphrase for keyslot Y, cryptsetup performs the correct actions.
> However, the message printed is "Key slot X unlocked". So in other
> words, cryptsetup tells the user it killed the keyslot they just used to
> unlock the action.
> 
> This is cosmetic, but has given me a jolt of fear at least once, and a
> fix should be extremely trivial. Perhaps print a message like
> 
> """
> Key slot Y unlocked
> Killed key slot X
> """

unfortunately i'm unable to reproduce this bug. for me, cryptsetup
1.1.0~rc2 doesn't report which keyslot it killed at all. only the
unlocked keyslot is reported:

# cryptsetup luksKillSlot /dev/vg_int/ctest 3
Enter any remaining LUKS passphrase: 
Key slot 2 unlocked.
Key slot 2 verified.
# cryptsetup --key-file=keyfile luksKillSlot /dev/vg_int/ctest 2
Key slot 1 unlocked.
Key slot 1 verified.
# cryptsetup luksKillSlot /dev/vg_int/ctest_pass 1
Enter any remaining LUKS passphrase: 
Key slot 0 unlocked.
Key slot 0 verified.

please paste the exact output of cryptsetup action.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100219/e8d98f06/attachment.pgp>