[Bug 524663] Re: cryptsetup: luksKillSlot reports incorrect slot unlocked

[Bug Watch Updater]

** Changed in: cryptsetup (Debian)
       Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/524663

Title:
  cryptsetup: luksKillSlot reports incorrect slot unlocked

Status in “cryptsetup” package in Ubuntu:
  Fix Released
Status in “cryptsetup” package in Debian:
  Fix Released

Bug description:
  Binary package hint: cryptsetup

  SEVERITY: MINOR

  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
  """

  Including below reportbug-style information as well as a sample
  execution on a loopback. Note that I found this bug operating on a
  real LVM partition, and have simply reproduced it on a loopback. I
  have added into the terminal output the passwords I used (a for
  keyslot 0, b for keyslot 1) so you can follow what I typed.

  Thanks for the free software, don't root me bro, and best of luck,
  Alex 

  ************************************************************************

  alexr at eternity:~$ sudo cryptsetup --version
  cryptsetup 1.0.6
  alexr at eternity:~$ cd /tmp
  alexr at eternity:/tmp$ sudo dd if=/dev/zero of=backing bs=4M count=10
  10+0 records in
  10+0 records out
  41943040 bytes (42 MB) copied, 0.0743792 s, 564 MB/s
  alexr at eternity:/tmp$ sudo losetup /dev/loop5 backing 
  alexr at eternity:/tmp$ sudo cryptsetup luksFormat /dev/loop5

  WARNING!
  ========
  This will overwrite data on /dev/loop5 irrevocably.

  Are you sure? (Type uppercase yes): YES
  Enter LUKS passphrase: a
  Verify passphrase: a
  Command successful.
  alexr at eternity:/tmp$ sudo cryptsetup luksAddKey /dev/loop5
  Enter any LUKS passphrase: a
  key slot 0 unlocked.
  Enter new passphrase for key slot: b
  Verify passphrase: b
  Command successful.
  alexr at eternity:/tmp$ sudo cryptsetup luksKillSlot /dev/loop5 0
  Enter any remaining LUKS passphrase: b
  key slot 0 verified.
  Command successful.
  alexr at eternity:/tmp$

  
  ************************************************************************

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Feb 19 13:00:14 2010
  Dependencies:
   libgcc1 1:4.3.3-5ubuntu4
   debconf 1.5.26ubuntu3
   libdevmapper1.02.1 2:1.02.27-4ubuntu5
   libtext-wrapi18n-perl 0.06-6
   udev 141-1.2
   libtext-iconv-perl 1.7-1build1
   sed 4.1.5-8
   ncurses-bin 5.7+20090207-1ubuntu1
   findutils 4.4.0-2ubuntu4
   procps 1:3.2.7-11ubuntu2
   libgcrypt11 1.4.1-2ubuntu1
   initramfs-tools 0.92bubuntu29
   lzma 4.43-14ubuntu1
   debconf-i18n 1.5.26ubuntu3
   libselinux1 2.0.65-5build1
   lsb-base 4.0-0ubuntu0.9.04.1
   coreutils 6.10-6ubuntu1
   libpam0g 1.0.1-9ubuntu1.1
   libstdc++6 4.3.3-5ubuntu4
   module-init-tools 3.7~pre9-2
   libpam-runtime 1.0.1-9ubuntu1.1
   libpam-modules 1.0.1-9ubuntu1.1
   passwd 1:4.1.1-6ubuntu6
   liblocale-gettext-perl 1.05-4build1
   cpio 2.9-15ubuntu1
   libvolume-id1 141-1.2
   libattr1 1:2.4.43-1
   libacl1 2.2.47-2
   debianutils 2.30ubuntu3
   libncurses5 5.7+20090207-1ubuntu1
   libc6 2.9-4ubuntu6
   libgpg-error0 1.4-2ubuntu7
   dpkg 1.14.24ubuntu1
   libklibc 1.5.14-1~exp1ubuntu2
   klibc-utils 1.5.14-1~exp1ubuntu2
   libpopt0 1.14-4
   dmsetup 2:1.02.27-4ubuntu5
   adduser 3.110ubuntu5
   busybox-initramfs 1:1.10.2-2ubuntu7
   perl-base 5.10.0-19ubuntu1.1
   libdb4.7 4.7.25-6ubuntu1
   libtext-charwidth-perl 0.04-5build1
   gcc-4.3-base 4.3.3-5ubuntu4
   libuuid1 1.41.4-1ubuntu1
  DistroRelease: Ubuntu 9.04
  Package: cryptsetup 2:1.0.6-7ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  Uname: Linux 2.6.30 x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/524663/+subscriptions