cryptdisk sets up partitions by index/device instead of uuid
Bug #509957 reported by
Flávio Etrusco
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
partman-crypto (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: cryptsetup
It's obvious cryptsetup should map partitions by UUID instead of dev entries (e.g. /dev/sda5) -- and it's obvious I don't know how difficult it is ;-) --, even more while cryptdisks service doesn't do enough validation on the partition used (https:/
Changed in cryptsetup (Ubuntu): | |
status: | New → Confirmed |
status: | Confirmed → New |
description: | updated |
To post a comment you must log in.
cryptsetup does map partitions by UUID, if that's how you specify them in /etc/crypttab. In the case of bug #509952, clearly you didn't do this, so of course cryptsetup wasn't mapping by UUID.
An entirely separate question is whether the parent device *has* a UUID. If you're not using LUKS, I think the answer is going to be 'no'.