You are not logged in.
Synopsys: Remote headers are not supported by systemd-cryptsetup.
I was able to get my root partition working with a remote header by adding the '--header=' parameter to the encrypt hook but my searches can only find reference to request for the addition of support to systemd-cryptsetup from about a year ago. I'd also like to have remote headers for my data partitions.
This is the entry in /etc/crypttab:
myRecordings /dev/sdc1 /opt/lK/cK.splashK1280x1024.jpg luks --header=/boot/myRecordings-header.img
...and this is the error I see in the systemd journal:
systemd-cryptsetup[314]: Encountered unknown /etc/crypttab option '--header=/boot/myRecordings-header.img', ignoring.
How do I confirm that support for the '--header=' parameter has been added (or not) to systemd-cryptsetup?
Last edited by KairiTech (2014-07-21 13:33:13)
Offline
Nope! There's no mention of the '--header=' parameter in the source so I created a script to manually mount my data partition using a remote header and keyfile until such time that remote header support is added to systemd-cryptsetup.
Last edited by KairiTech (2014-07-21 15:32:20)
Offline
Looks like this was added to systemd recently:
You can find "header" in the source now.
http://cgit.freedesktop.org/systemd/sys … 7376e83528
https://bugs.freedesktop.org/show_bug.cgi?id=66396
I upgraded to testing to try this out and it works. I am using the remote header option and lvm on luks.
No more hacks are required, it is all implemented in systemd now.
EDIT:
This is already mentioned in the wiki here:
https://wiki.archlinux.org/index.php/Dm … _initramfs
Last edited by teateawhy (2015-02-18 00:18:57)
Offline