Package: cryptsetup-run Version: 2:2.0.3-4 Severity: normal The latest version of cryptdisks_start seems to have dropped support for regular files containing the data for an encrypted loopback mount. With 2:2.0.3 it seems that the scripts' sanity checks will only accept block devices, and give the error "skipped, device $CRYPTTAB_SOURCE does not exist" for regular files.
I'd normally do # cryptdisks_start user_clientdev_crypt # mount /home/clientdev/workspace/ # cryptdisks_start user_clientdev_crypt [FAIL] Starting crypto disk...user_clientdev_crypt (skipped, device /home/.clientdev_crypt does not exist)...failed. # file -s /home/.clientdev_crypt /home/.clientdev_crypt: LUKS encrypted file, ver 1 [aes, xts-plain64, sha1] UUID: a81e1598-9f69-44be-986a-dde68bdcac54 # ls -l /home/.clientdev_crypt -rw-r--r-- 1 root root 536870912000 Jul 2 13:18 /home/.clientdev_crypt # grep client /etc/crypttab user_clientdev_crypt /home/.clientdev_crypt none luks,discard,noauto # grep client /etc/fstab /dev/mapper/user_clientdev_crypt /home/clientdev/workspace/ ext4 noauto 0 0 Regards, Steve -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cryptsetup-run depends on: ii cryptsetup-bin 2:2.0.3-4 ii debconf [debconf-2.0] 1.5.67 ii dmsetup 2:1.02.145-4.1 ii libc6 2.27-3 cryptsetup-run recommends no packages. Versions of packages cryptsetup-run suggests: ii dosfstools 4.1-2 pn keyutils <none> ii liblocale-gettext-perl 1.07-3+b3 -- debconf information: * cryptsetup/prerm_active_mappings: false