DirIV poisoning mitigation, file size obfuscation

[emerajid]

More of a documentation expansion suggestion. Both the DirIV poisoning mitigation and file size obfuscation can be (hopefully) easily achieved by changing nothing at all in gocryptfs itself.

$ truncate -s 1G fs0
$ /sbin/mkfs.ext4 -E root_owner fs0
$ udisksctl loop-setup -f fs0
$ udisksctl mount -b /dev/loopX

Literally as simple as that. The only problem is udisks. If there was a (good, stable) read write FUSE based filesystem that worked with image files, then we could have an entirely FUSE solution that is basically perfect. No developers' efforts wasted at all, only as much performance lost as is needed. Maybe you shouldn't create 16TB files though, I don't really know.

Any thoughts on this?

[emerajid]

So I tried libguestfs-tools, but the performance is abominable compared to loopback mount. It was barely 5mb/s at its best. I used raw disk image, handcrafted as per https://unix.stackexchange.com/questions/281589/how-to-run-mkfs-on-file-image-partitions-without-mounting