I’m hacking away at simlink/binding dom0 folders to Veracrypt containers.
I’m not sure what’s happening on the backend of Veracrypt, but often when
opening the container, the file permissions/ownership is changed.
I’m hoping I can open the container, bind the folders, then run the ownership
repair scripts, and everything will work as it should, mount to mount.
I am not familiar with veracrypt but a quick research suggests that
ownership is a common issue.
eg:
my 2cents tip: Before looking to correct the ownership after the
container is mounted, try first to mount the container with the
necessary options so the permissions won’t change at all.