Thank you Alvaro! I tried both options B & C you mentioned they work similarly (as expected) to what I had tried, which is that they override all the permissions, whereas I need to maintain the permissions.ġ. More than happy to assist, just share why/what you want this, so I can can understand.Īt this moment, I will say go for my suggestion C or B If you were using linux/osx -> nfs -> linux guest, sure, you willīut in any other combination, i don't think it will, and is not required to be. Why do you expect see the same permissions from the windows bash inside the vm? Now, with this little explanation, can I ask.

Use virtualbox sharefolder and set gid/uid/dmode=770/fmode=660 and make the user that will use these files to have acess to use it will mount then will be able to read/write etc.ī. If the user that is trying to mount have user or group access, and match, etc. Use windows filesharing and samba client on the guest, so windows will do the checks on user/group but this is not rwx rwx rwx or user-group-other So trying to see on the linux guest what you have in windows over virtualbox shared folder will be probably a big headache.Ī. Vfat/fat32 they only do 777 for directories and 666 for files Ntfs have some sort of ACL (access control list) You will see a lot of information, but no permissions at all. The guest is linux, so, linux understand what rwx rwx rwx are user-group-otherīut, neither virtualbox shared folder neither windows have those permissions Please, relax, what I am going to write can be sound weird (it's weird actually)īut, you have 2 Filesystems that are not a real filesystem.

Virtualbox shared folders permissions