[Bug 324871] Re: cryptsetup: Cannot delete a Keyslot from itselfs

[Bug Watch Updater]

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

** Changed in: cryptsetup
       Status: Fix Committed => 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/324871

Title:
  cryptsetup: Cannot delete a Keyslot from itselfs

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

Bug description:
  Binary package hint: cryptsetup

  lsb_release -rd :
  Description:	Ubuntu 8.04.2
  Release:	8.04

  apt-cache policy cryptsetup :
  cryptsetup:
    Installed: 2:1.0.5-2ubuntu12
    Candidate: 2:1.0.5-2ubuntu12
    Version table:
   *** 2:1.0.5-2ubuntu12 0
          500 http://archive.ubuntu.com hardy/main Packages
          100 /var/lib/dpkg/status

  The bug I reported for debian (etch/lenny) also exists under debian
  hardy.

  see : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513596

  It is not possible to "suicide" a luks encrypted disk, however it is a
  "feature" (there is a warning message before doing that)

  This is the output that explains the problem :

  root at computer:~# cryptsetup luksFormat /dev/loop0 key0.bin

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

  Are you sure? (Type uppercase yes): YES
  Command successful.
  root at computer:~# cryptsetup luksAddKey --key-file key0.bin /dev/loop0 key1.bin 
  key slot 0 unlocked.
  Command successful.
  root at computer:~# cryptsetup luksDelKey --key-file key0.bin /dev/loop0 0
  key slot 0 unlocked.
  No remaining key available with this passphrase.
  Command failed.
  root at computer:~# cryptsetup luksDelKey --key-file key0.bin /dev/loop0 1
  key slot 0 unlocked.
  Command successful.
  root at computer:~# cryptsetup luksDelKey --key-file key0.bin /dev/loop0 0

  WARNING!
  ========
  This is the last keyslot. Device will become unusable after purging this key.

  Are you sure? (Type uppercase yes): YES
  key slot 0 unlocked.
  No remaining key available with this passphrase.
  Command failed.

  
  A patch solving this issue for hardy is attached

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