[Bug 474258] Re: Extremely dangerous! cryptswap killed my partition

[Tuomas Heino]

Another alternative (besides using a file on some fs) would be using LVM volumes, and not resolving the related symlinks.
Then /etc/crypttab would look something like:
cryptswap1 /dev/mapper/swap-swap_1 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

where /dev/mapper/swap-swap_1 is a symlink maintained by device mapper.
It should NOT be resolved to target of the symlink (like /dev/dm-1)
before writing to crypttab, since target of that symlink is dynamic.

-- 
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/474258

Title:
  Extremely dangerous! cryptswap killed my partition

Status in “cryptsetup” package in Ubuntu:
  Triaged
Status in “cryptsetup” source package in Precise:
  Triaged
Status in “cryptsetup” package in Debian:
  New

Bug description:
  Binary package hint: cryptmount

  9.10 installed with encrypted "home".
  Had root on /dev/sda1, swap on /dev/sda2, and manually created "data" partition on "/dev/sda3"
  When I deleted /dev/sda2 partition (wanted to move swap to the second HDD) - ubuntu killed my "data" partition!
  I suppose the problem is that /dev/sda3 became /dev/sda2 and the cryptswap utility just killed all the data (about 80 gigs!), because /dev/sda2 is in the /etc/crypttab file as a swap partition...
  Cryptswap should check the type of partition before mounting it as swap.

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