Paul Olaru

Probably to be expected, given that all graphics are done in software?

Subscribing here as a vote that I also would like this feature (it's a "make or break" for me)

[bump] I don't like having my recovery key or user password in fstab, even if I have LUKS -- I cannot remote into my machine as fstab is readable by...

@alysher The question was how we get the file, not how we use it.

Just as an issue, handling TPM with default settings is impossible. This has to be stated in the documentation if it isn't already.

--user-password works for passwords in the "data-like" (without TPM) password-only protection. It doesn't work with TPM and PIN/password which is used to unlock the TPM. In fact, TPM will refuse...

Maybe you need to do `losetup -d` on where you have bound dislocker-file? If you did it manually. Mounting with -o loop should automatically clean the loop device setup but...

Mounting with normal mount command and fuse.dislocker type seems to work in my case (fstab support). In that case it does show correctly.

Never mind, now it shows an oddity: the directory where I have the cloned source. Not an executable. My fstab: /dev/sdb5 /mnt/dislocker-mount fuse.dislocker user-password=pass 0 0 /mnt/dislocker-mount/dislocker-file /media/Common\040Data ntfs uid=1000,gid=1000,dmask=022,fmask=133,uhelper=udisks2,nodev,nosuid,loop,nofail...

FUSE uses /dev/fuse as the channel between kernel and user for the mounts.