Curtin cannot create dmcrypt devices on precise and dmcrypt configuration syntax is not consistant with other storage entries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Curtin cannot create dmcrypt devices on precise because the older version of cryptsetup has a different set of flags.
Also, the configuration format for dmcrypt devices uses 'dm_name' to specify the name of a cryptsetup device, rather than 'name' as used elsewhere in storage configuration. There are many options for configuring cryptsetup that are not supported by the storage configuration format for dmcrypt devices.
Finally, there is no secure way to get a key to the installation, as currently the key must be specified in plaintext in a world readable file.
Since encryption is not used by MAAS right now, this is really low priority, but since there may be a need for this functionality at some point in the future, I'll leave a bug open to track the issues with curtin dmcrypt configuration.
Changed in curtin: | |
status: | New → Confirmed |
Changed in curtin: | |
importance: | Undecided → Wishlist |
Log showing failure to run cryptsetup on precise during storagetests