Open 7flying opened 1 year ago
What format does the "disk_label" option take? Ultimately we should be able to discover the LUKS partition quite easily, whether by lsblk (probably not) or some API in cryptsetup and associated rust bindings.
What format does the "disk_label" option take? Ultimately we should be able to discover the LUKS partition quite easily, whether by lsblk (probably not) or some API in cryptsetup and associated rust bindings.
It's a string, we usually need '/dev/vdaX' or something like that.
so, it's not really a label, it's more a /dev path - perhaps @puiterwijk remembers more
The
DiskEncryptionClevis
FSIM requires adisk_label
configuration option to apply the given clevis bindings. Make this optional and if so, the client should infer which disk label the encryption options should be applied to by looking for the LUKS device.Out of scope: handling multiple LUKS devices.
Acceptance criteria:
DiskEncryptionClevis
FSIM no longer requires an explicitdisk_label
to workdisk_label
is given the client-linuxapp will identify which single device the encryption settings will be applied todisk_label
vs nodisk_label
)