Page 1 of 1
file permissions on vbox shared folder
Posted: 29. Jul 2008, 14:26
by mbunal
hi all
my host system is pardus linux. i run windows xp with vbox. i set up vbox sharing folder. and i can use it. any file or folder operations has no error. anyway
when i create a file from my vbox'd windows, it has a chmod 600 permission. when i create a file from pardus, it has a 644 permission. that is th my problem.
i want all files permissions 644, not 600.
can anyone help me?
baris.
Posted: 29. Jul 2008, 19:09
by Sasquatch
Create a script to do it automatically on certain times? What folder are you sharing? Is it a folder in your Home Directory? If so, than it's logical, as only you should be able to write to it and nobody else.
Posted: 29. Jul 2008, 20:22
by mbunal
Sasquatch wrote:Create a script to do it automatically on certain times?
it is not usefull solution. i already use manuel script. but it is very boring. after every save i must set permissions.
Sasquatch wrote:What folder are you sharing? Is it a folder in your Home Directory?
my shared folder under my home dir. /home/baris/www
Sasquatch wrote:If so, than it's logical, as only you should be able to write to it and nobody else.
i dont understand what u mean?
Posted: 29. Jul 2008, 20:56
by Sasquatch
Your home folder is a personal folder, meaning no other user should have access to it. If you would create a new user, you would not be able to access the new user's home folder with your account and vice versa. By changing the permission you create a security risk too. Why do you want to change it anyway? If you run a website, isn't it better to run that outside your home folder? You can easily create a new folder and make yourself the owner of it and set it to 644 permissions.
Posted: 29. Jul 2008, 21:21
by mbunal
where ever i create a folder there is same problem. when i create a folder from vbox's windows it has 600 not 644. it is not impoartont to me thar folder where it is? inside home or root. i dont want any other script or such things to change permission to 644.
but i think there is no solution. maybe only samba shares.
anyway thanks a lot.
Posted: 29. Jul 2008, 23:07
by Sasquatch
Are you sure that a shared folder on /virtualboxshare will give the same 600 permissions? As I have an NTFS drive that I share with SF, it has the same permissions when I create a file or folder on it using the Guest as if I use the Host system. But then again, I have it mounted with some additional options. Just try this and report back.
Posted: 30. Jul 2008, 11:53
by mbunal
ok. i use pardus linux as host system. i setup windows xp in vbox. i share a folder /home/baris/www on host (pardus linux). when i write any file on this shared folder from vbox it has 600 (on host's files system which is ext3).
i dont write anything ntfs, i dont share anything on ntfs.
i write on ext3 file system via vbox shared folder.
Posted: 30. Jul 2008, 19:18
by Sasquatch
I hate repeating myself, but I guess I have to. Create a folder /virtualboxshare and give yourself ownershipt and 644 permissions on it. Now access that folder through shared folders and put a file (doesn't matter what) on it and check with the Host what permissions it has. Does it have 644 or 600?
Posted: 31. Jul 2008, 10:33
by mbunal
it has 600.
i solved it with samba. but i research still to solve with vbox shared folder.
Posted: 31. Jul 2008, 10:59
by h1d
Does vboxsf turn it into 600 in a hard coded way?
Re: file permissions on vbox shared folder
Posted: 4. Aug 2008, 14:21
by DaveK
mbunal wrote:
my host system is pardus linux. i run windows xp with vbox. i set up vbox sharing folder. and i can use it. any file or folder operations has no error. anyway
when i create a file from my vbox'd windows, it has a chmod 600 permission. when i create a file from pardus, it has a 644 permission. that is th my problem.
This is also bug 1776:
http://www.virtualbox.org/ticket/1776
The shared folders driver is not fully implemented yet and does not correctly convey permissions between the host and guest sides.
Posted: 26. Aug 2008, 17:42
by gazmond
I have this problem too and it's a pain. 600 is too restrictive and I need to be able to override it. For now, I've had to use sudo on the Linux host to get around the problem but it isn't ideal.