Bug 1869 - Unix Extensions: Wrong Handling of permission changes
Summary: Unix Extensions: Wrong Handling of permission changes
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.7
Hardware: All Linux
: P3 normal
Target Milestone: none
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-03 15:14 UTC by Michael Holzt
Modified: 2006-04-08 22:55 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Holzt 2004-10-03 15:14:13 UTC
When trying to setup a new linux pool which mounts home dirs from remote by
using cifs, i noticed that there seems to be a bug in the handling of the
permissions when changing them.

In particular it seems that samba enforces permission not to be more than the
create mask, even when changing it. If i have the "create mask" set to 0600 in
samba.conf (which is a reasonable value), a user can not set the executable flag
of the file. He can set and remove the read and write flags, and can remove an
executable flag from a file which has already one - but can not set it again.

When setting "create mask" to 0700, the user can modify all three flags (read,
write, executable) without problems, but every new file created would be
automatically 0700 which is not what i want.

I tried playing with "security mask" and other options but found no solution. It
seems i'm not the only one, who has notices this problems, on google i found the
following report which is the same problem:
http://lists.samba.org/archive/samba/2004-July/089533.html

I think this is a bug, because the "create mask" value should not make any
difference when modifying an already existing file.
Comment 1 Gerald (Jerry) Carter (dead mail address) 2005-02-17 10:09:55 UTC
does this still exist in 3.0.11 ?
Comment 2 Gerald (Jerry) Carter (dead mail address) 2006-04-08 22:55:20 UTC
Please retest against a current release and reopen if the issue still exists.