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
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/474258/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
