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

[zatoichi0]

I had this continue trashing my new partition at every reboot and I
couldn't track the cause ...

One idea/workaround with the UUID:

 - have cryptsetup allow only files or UUIDs instead of devices until
UUID support is in the swap filesystem, e.g.:

     partition ->
         "containing" ext3 filesystem with a UUID ->
              file used as encrypted swap

This way UUID can be used even now.

While there is another level of indirection (file -> fs), the security
is a performance tradeoff anyway.

The logic for cryptsetup could be changed for now to:

 - create a swap partition with an ext2 filesystem with a swap file
taking all the space

 - allow only UUIDs in crypttab and expect a single file at that
location

This would allow an easy transition once UUID support is present and
even "upgrading" the file to a UUID-marked cryptswap partition.

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