GNOME Bugzilla – Bug 104052
Nautilus not following SGID bit
Last modified: 2006-04-05 04:33:50 UTC
Description of Problem: I have a directory /shared that I have done a "chown -R nobody.shared /shared && chmod -R 2774 /shared" so that all files are created with the owner set to shared and permisions on 774. Nautilus does not acknolegde this when copying files. Steps to reproduce the problem: 1. Create a directory as described above 2. Copy a file from else where into this directory using nautilus 3. Note the gid of the file is incorrect, stays as previous, should changed to "shared" Actual Results: File retains it's permisions / owners Expected Results: File owner set to $user.shared and permissions 774. How often does this happen? Every time. Additional Information: Now test from the command line, copying the same file, something like "cp /home/damien/music/goodmusic.ogg /shared/". This should make the file in /shared owned by damien.shared permissions 774. Nautilus keeps the permissions / owners from original location/file.
Specified version number.
I can confirm this action also. i have a simliar setup and i can make a file in directory has correct permissions. i can copy file over with konqueror and it has the correct permissions but if i copy a file with nautalis shows the group as my primary group. not the group that owns the directory that has the SGUID bit set. I am using Red Hat 8.0 will all errata applied.
*** Bug 133272 has been marked as a duplicate of this bug. ***
Confirmed in nautilus 2.6.0, could someone please update the Version of this bug to (at least) 2.6.0? This bug is a security problem for people working in shared environments, where file permissions are maintained through the use of sticky bits. I use directories where maintaining file permissions and group settings is fundamental to security. Could someone please update the severity of this bug to "Critical" since this is a security issue. Has there been any progress on this?
I have increased the version number as per comments. I have also upgraded the serverity to Critical and await the wrath of someone saying it was not my place to do so.
Created attachment 34665 [details] [review] Proposed patch Proposed patch to check target dir SGID and set group accordingly
*** Bug 164999 has been marked as a duplicate of this bug. ***
that's a gnome-vfs issue, reassigning to the right place, updating the version
Actually reassigning to the vfs maintainers :)
fix in cvs
*** Bug 155492 has been marked as a duplicate of this bug. ***
This problem is reoccuring now with gnome-vfs2-2.14.0-2 We need to get this fixed ASAP, as it is breaking the unix security model