Investigate BitLocker support limitations and possible ways around them

[nohajc]

Hello,

I think I have a similar Issue:

macOS: disk: /dev/disk4s2
macOS: rdisk: /dev/rdisk4s2
macOS: media_writable: true
macOS: label: Some("TORSTEN-YOGA7 TOSHIBA EXT 06.02.2022")
macOS: fs_type: Some("BitLocker")
macOS: uuid: Some("b9df779e-5cab-468f-aeaa-2167cd63fbcc")
macOS: mount name: TORSTEN-YOGA7_TOSHIBA_EXT_06.02.2022
macOS: root_path: /Users/torstenschneider/.anylinuxfs/alpine/rootfs
macOS: num_vcpus: 1
macOS: ram_size_mib: 512
macOS: vmproxy args: ["/vmproxy", "/dev/vda", "TORSTEN-YOGA7_TOSHIBA_EXT_06.02.2022", "-b", "127.0.0.1", "-t", "BitLocker", "-o", "uid=501,gid=20", "-d", "/dev/vda"]
macOS: Using vsock for VM control socket
Linux: Received command: 'SubscribeEvents'
Linux: Enter passphrase for /dev/vda:
Linux: BITLK devices with type 'encrypt-on-write' cannot be activated.
Linux: Sent report to vmctrl client
Linux: Error: Failed to open encrypted device '/dev/vda': 1
macOS: NFS server not ready
macOS: libkrun VM exited with status: 1
macOS: VM report received
macOS: Kernel log saved to /Users/torstenschneider/Library/Logs/anylinuxfs_kernel.log
macOS: gvproxy exited with status: 0

Originally posted by @BigWilliStyle80 in #111 (comment)

[nohajc]

Seems like some types of encrypted volumes are not supported by cryptsetup. How does it compare to dislocker or any other alternatives?