VirtualBox disrespects umask when creating files in shared folders => Fixed in SVN

[László Monda]

I want my WinXP guest to create files using shared folders on the filesystem of my Gutsy host with the permission 644. I set umask to 0022, but VirtualBox creates files with permission 600.

I've even modified the VirtualBox script right before

exec "/usr/lib/virtualbox/VirtualBox" "$@"

to include

umask 0022

but VirtualBox obviously disrespects umask by creating files with permission 600.

[Andrew]

I acknowledge this bug and propose it being fixed.

Is there a quickfix?

[Dimas Souza]

I acknowledge this bug also and propose it being fixed.

Is there a workaround?

[Dimas Souza]

btw: I am using VirtualBox 2.1.2r41885

[Dimas Souza]

More info: When creating directories, the permissions are bein correctly created.

[pt]

omg i am retarded

[P. Meiser]

I would also be interested in a solution.

[Marc Schütz]

The problem is that VirtualBox specifies a mode of 0600 when creating a file. This can be trivially fixed by using 0666 instead, which would then automatically be combined with the umask to yield 0644 (see the attached patch vbox-umask.patch).

However, I do not know the reason why 0600 has been used there in the first place.

[Matt Kynx]

This is a big one for me (OSX host, Linux guest). If I mount a group-writable directory, when users in that group create files they can't even read them!

I can understand it if the guest OS doesn't support the concept of a umask - perhaps then the solution would be to add a 'cmode' option to the mount command? But if OS does support umask wouldn't it make sense to honour it?

[P. Meiser]

Issue is also present in 2.2.0 beta2.

[Frank Mehnert]

A simple fix will be contained in the upcoming release. The file permissions will be 0222 if the guest opened the file write-only, 0444 if the guest opened the file read-only and 0666 if the guest opened the file with read/write permissions.

[P. Meiser]

works perfectly in 2.2.0. From my POV, this ticket can be closed.

[P. Meiser]

Issue is there again with 3.0.0.

[umoeller]

Fixed in 3.0.2.

[pepijnve]

I'm getting this behavior again in 3.1.6. getfacl output of all existing directories is

# file: Snapshots/
# owner: root
# group: vboxusers
# flags: -s-
user::rwx
group::rwx
mask::rwx
other::r-x
default:user::rwx
default:group::rwx
default:mask::rwx
default:other::r-x

However, newly created files get rw-------.

[P. Meiser]

Same for me with 3.1.6, although all files have permission 666 instead of 644 (as my umask is 0022).

[Marc Schütz]

I can confirm this regression with 3.2.4. Btw, the permissions are correct when the file is created via Right Click -> New -> ... in Windows Explorer; but in Office (2007 here) it sets 666 instead of 644.

[Frank Mehnert]

To be sure: Which was the last working VBox release for you?

[Marc Schütz]

For me it was 3.1.4, but I did not test anything in between that version and the current one.

[Frank Mehnert]

Works fine here when creating a file manually or saving a page from the internet explorer. Linux host, WinXP guest. Do you have some simpler test? Don't have Office available here...

[Marc Schütz]

This bug is still there in version 3.2.6.

[Frank Mehnert]

Well, if you don't answer my question I cannot help you.

[Marc Schütz]

No, I don't have a simpler test. But as you don't have office, I guess you still cannot help me.

[Marc Schütz]

This bug is still present in 4.0.8.

[Jordi]

This bug is still present in 4.1.18 and there's a similar ticket ​#10534

I wonder how such an important and basic issue keeps unsolved after 4 years!

[Frank Mehnert]

This bug has nothing to do with #10534. And if you would take some time and actually read the above comments then you would observe that there is no simple test case to reproduce the problem of this ticket.