owner of shared public folder is nobody

Bug #284651 reported by Phoenix
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

I have a folder named ~/public which I want to be shared and writeable by anyone, so I create in nautilus the needed settings and I can access the folder from remote and write files into it, everything fine. But on the host, where the files have been written to, they files are owned by the user "nobody", which renders the user unable to use the files as if they were his, like deleting the files. If the files would be owned by the user everything would be fine.

Revision history for this message
Elias K Gardner (zorkerz) wrote :

I have run into this problem too. Correct me if im wrong but your suggestion would make files owned by multiple people (depending on the person accessing them)? Im not sure this is possible. Either way this is a problem I have had trouble with in the past as well.

Revision history for this message
Phoenix (phoenix-dominion) wrote :

Sorry if I'm missleading, no, currently files are owned by the user nobody and the primary group of the user taht created the directory - probably because the directory that is shared is user and group owned by the user. What I want is, that new files are owned by the user you have to see:

I share as "Public" my "/home/me/Public

now if someone puts some files into it, then I can open them, but I can't delete them - as I'm not the owner of the files, I have to get root and chown thoses files or access my local filesystem via samba to delete thoses files, either way is not quite straight forward.

Revision history for this message
Elias K Gardner (zorkerz) wrote :

Yes ok that makes it all clear to me i think. Its an odd problem because the person who put them there is using samba and can then delete them if you gave the read/write access but you cannot because normally you would not access the folder with samba or as root. I have a share folder much similar and agree this is a large annoyance.

Revision history for this message
Dan Trevino (dantrevino) wrote :

 Thank you for taking the time to report this issue and helping to make Ubuntu better. You reported this issue a while ago and there hasn't been any activity in it recently. We were wondering if this is still a problem for you.

Revision history for this message
cornergraf (x-launchpad-cornergraf-net) wrote :

This is most certainly still a problem.

1) Create a shared folder with guest and write permissions
2) access shared folder from windows XP and crate some files/folder
3) in ubuntu when accessing the shared folder, the files created in step 2 are locked because they are owned by user "nobody"

Files created in a shared folder should inherit permissions and owner settings from the shared folder.

Changed in ubuntu:
status: Incomplete → Confirmed
Revision history for this message
Bartong (barton-guy) wrote :

This is still an issue in Karmic.

The only fix I have found is to set 'create mask = 0777' and 'directory mask = 0777' in the [global] section of /etc/samba/smb.conf

I had originally tried to set these parameters in /var/lib/samba/usershares/<sharename> but they do not seem to work in there.

I also tried using the 'inherit owner = yes' parameter, but this resulted in other clients not being able to write to the server.

Revision history for this message
rduke15 (rduke15) wrote :

Beware that the workaround in comment #6 will apply these 777 permissions to ALL shares defined in Samba. So this doesn't really work if you also use Samba for other non-Public shares.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.