cryptset incompatible to Debian's cryptsetup
Bug #5360 reported by
Rüdiger Kuhlmann
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cryptsetup (Ubuntu) |
Fix Released
|
Medium
|
MOTU | ||
Bug Description
Mounting encrypted partitions created with Debian sarge's cryptsetup
fails. This is because Ubuntu's cryptsetup supports LUKS, but does
not give an option to fall back to the non-LUKS way. Luckily, those
partitions can still be accessed by using cryptoloop.
Also, the included mount.crypt neither works for ordinary users, nor
does it clean up the dm-crypt mapping on unmount, so that re-mounting
will fail.
Revision history for this message
| hunger (hunger) wrote | #1 |
Revision history for this message
| Sebastian Dröge (slomo) wrote | #2 |
| Changed in cryptsetup: | |
| status: | Unconfirmed → Fix Released |
To post a comment you must log in.
I am mounting LUKS and non-LUKS partition from my crypttab.
cryptsetup in ubuntu does still support "the old way", so I do not see why it should fail to mount debian/sarge partitions. Maybe the key sizes/hash algorithmns do not match?
If you feel adventurous you could try my init script from #563 (I am using it since hoary, so it shouldn't be too bad;-)... that "autodetects" whether a partition is created using LUKS or not and mounts it accordingly.