Matthew Lee

Sorry for the slow reply, I managed to find a temporary fix try this: sudo veracrypt --filesystem=none --mount /dev/sdb1 /media/something/ (Now you can apply other filesystem mount options and they will work as they are being passed to mount in the command below) You can now see it is semi-mounted to veracrypt1, now do this: sudo mount -o umask=000 /dev/mapper/veracrypt1 /media/something/ To unmount just do sudo veracrypt -d Been crammed with work at the moment so I've been unable to debug the program...

Hi Gary, thank you so much, I got your email and it was extremely helpful!

Unfortunately, exFat does not allow for setting of permissions or changing of ownership, since it does not support file permissions. Therefore, to allow all users on the server to access an external exFat drive it would need to be mounted using 'umask=000'. I have been trying to set my computer up with the source code so I could debug it, to find out if it is indeed a problem with veracrypt. However, I'm currently having trouble getting hold of 2010 C++ & Visual C++ 1.52.

Exactly, it mounts but the parameter 'umask=000' fails to have any conquence, likewise, with other arguements too such as 'uid=0,gid=0', when not using veracrypt and mounting normally 'mount', these commands work hence I think there is a bug in veracrypt or I'm doing something wrong (sorry for the delayed replies I don't know how to push responses)

I have, this also does not work :(

Does anyone know if providing the file system mounting options via the command line using --fs-options is working? I have been trying to mount an exfat drive with the addition of '--fs-options=umask=000' on Linux Mint and on Pi 3. I can successfully mount a non-encrypted drive normally using 'mount -o umask=000 /dev/sda1 /media/someFolder', this allows the exFat drive to be seen by all users which is my goal. However, I can't reproduce the same results using an encrypted drive with veracrypt. Using:...