On 11/29/18 10:43 AM, Carabus wrote: Hi,
buster /dev/disk/by-id/xxxx none luks,header=/dev/disk/by-uuid/xxxx
Is it just simplified example or do you really pass identical string to both header= and data device parameters?
where header have exact uuid of second partition of usb flash (crypto_LUKS) but cryptsetup say, i`m do it wrong cryptsetup: WARNING: Target buster has an invalid header /dev/disk/by-uuid/xxxx
I can't find this message anywhere in cryptsetup source code. What cryptsetup version did you use? (But I guess this error message originates in systemd-cryptsetup binary since it's systemd-cryptsetup what unlocks devices put in crypttab if you run distro with systemd)
but this header work fine when open with this command: cryptsetup open /dev/disk/by-id/xxxx --header /dev/disk/by-uuid/xxxx buster
In that case it's probably bug in systemd crypttab handling.
would you please give me examples of crypttab `header=` option which will work?
I don't think you did anything wrong. From crypttab documentation you should be able to pass same value in header= option of crypttab line as you would do with cryptsetup --header option.
Regards O. _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx https://www.saout.de/mailman/listinfo/dm-crypt
