cryptsetup should support block devices without filesystems
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cryptsetup (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
With the rise of newer filesystems, there are devices which may not actually contain a filesystem, but are used, i.e. as a caching device.
Case in point; I have a HDD and a SSD (a combination which is getting more and more common). My HDD contains a ZFS filesystem, the SSD is used as a "cache".
The same holds true for systems such as bcache.
However, to be safe, one may wish to encrypt these filesystems. Encrypting the cache is then also a good thing, as the cache may contain data equally sensitive.
However, when using a LUKS encrypted volume, the initramfs "cryptsetup" (in local-top) script checks the output from blkid, and errors out if the the device cannot be found in blkid.
I propose an extra option passed via /etc/initramfs-
A patch is attached to this bug report.
| Roel Brook (rainmaker52) wrote | #1 |
| Ubuntu Foundations Team Bug Bot (crichton) wrote | #2 |
| Changed in cryptsetup (Ubuntu): | |
| importance: | Undecided → Wishlist |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in cryptsetup (Ubuntu): | |
| status: | New → Confirmed |
| Matthew X. Economou (xenophon+ubuntu) wrote | #4 |
The attachment "cryptsetup.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]