I just received a new USB flash drive, and set up 2 encrypted partitions on it. I used dm-crypt (LUKS mode) through cryptsetup. With an additional non-encrypted partition, the drive has the following structure:/dev/sdb1, encrypted, hiding an ext4 filesystem labelled Partition 1./dev/sdb2, encrypted, hiding another ext4 filesystem, labelled Partition 2./dev/sdb3, clear, visible ext4 filesystem labelled Partition 3.Because the labels are attached to the ext4 filesystems, the first two remain completely invisible as long as the partitions haven't been decrypted. This means that, in the meantime, the LUKS containers have no labels. This is particularly annoying when using GNOME (automount), in which case the partitions appear as x GB Encrypted and y GB Encrypted until I decide to unlock them.This isn't really a blocking problem, but it's quite annoying, since I really like my labels and would love to see them appear even when my partitions are still encrypted.Therefore, is there a way to attach labels to dm-crypt+LUKS containers, just like we attach labels to ext4 filesystems? Does the dm-crypt+LUKS header have some room for that, and if so, how may I set a label?Note that I don't want to expose my ext4 labels before decryption, that would be silly. I'd like to add other labels to the containers, which could appear while the ext4 labels are hidden.
How can I set a label on a dm-crypt+LUKS container?
partition;gnome;luks;dm crypt;cryptsetup
I think the solution is to write udev rules like this.KERNEL==sd*, ENV{ID_FS_UUID}==your-sdb1-uuid, ENV{ID_FS_LABEL}=Partition_1, ENV{ID_FS_LABEL_ENC}=Partition_1KERNEL==sd*, ENV{ID_FS_UUID}==your-sdb2-uuid, ENV{ID_FS_LABEL}=Partition_2, ENV{ID_FS_LABEL_ENC}=Partition_2