This bug report really does not sound like it refers to the "cryptmount" package.
Specifically, "cryptmount" does not use the /etc/crypttab file for any purpose, nor does it include any utility called "cryptswap" (even though if offers similar generic functionality). More generally, it would appear that the problem is a side effect of repartitioning the main hard disk and not updating configuration files that refered to existing partitions that had been reassigned. It doesn't sound realistic for repartitioning tools to attempt to inform all applications that depend on a particular partition being available that it has been renamed. This is surely the responsibility of the system administrator. Naturally, I commiserate with the bug-submitter about the possible loss of 80GB of data. However, the proposed solution of checking partition-types before "mounting" as swap does not seem to offer an effective protection against corrupting data held on raw devices, especially via loopback devices which don't directly have "types" in the same way as disk partitions. Similar risks would seem to apply to any system-management tool which writes to raw devices. -- Extremely dangerous! cryptswap killed my partition https://bugs.launchpad.net/bugs/474258 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
