cryptsetup: when unlocking always put path to the object into Id
authorMichal Sekletar <msekleta@redhat.com>
Tue, 12 Dec 2017 16:49:14 +0000 (17:49 +0100)
committerMichal Sekletar <msekleta@redhat.com>
Tue, 12 Dec 2017 17:28:08 +0000 (18:28 +0100)
commit5a9f1b05ed6dad48958097fb37811668e69447fb
tree7a07b94fccc6ee1f06e0d5b52143beac621b65fc
parentcb9eeb062c323391fcd98da0c30e844fa5162e90
cryptsetup: when unlocking always put path to the object into Id

Some ask-password agents (e.g. clevis-luks-askpass) use Id option from
/run/systemd/ask-password/ask* file in order to obtain the password for
the device.

Id option should be in the following format,
e.g. Id=subsystem:data. Where data part is supposed to identify object
that ask-password query is done for. Since
e51b9486d1b59e72c293028fed1384f4e4ef09aa this field has format
Id=cryptsetup:/dev/block/major:minor when systemd-cryptsetup is
unlocking encrypted block device. However, crypttab also supports
encrypted image files in which case we usually set data part of Id to
"vol on mountpoint". This is unexpected and actually breaks network
based device encryption as implemented by clevis.

Example:
$ cat /etc/crypttab
clevis-unlocked /clevis-test-disk-image none luks,_netdev
$ systemctl start 'systemd-cryptsetup@clevis\x2dunlocked.service'
$ grep Id /run/systemd/ask-password/ask*

Before:
$ Id=cryptsetup:clevis-unlocked on /clevis-test-disk-image-mnt

After:
$ Id=cryptsetup:/clevis-test-disk-image
src/cryptsetup/cryptsetup.c