summaryrefslogtreecommitdiff
path: root/packaging4
diff options
context:
space:
mode:
authorJeremy Allison <jra@samba.org>2009-12-23 17:19:22 -0800
committerJeremy Allison <jra@samba.org>2009-12-23 17:19:22 -0800
commit6dcbb84d485b8a8ccf0c3a70d9f5f7e951aaf1c6 (patch)
tree02dd86f6643a7da76c01c3d37cb6e25677532499 /packaging4
parent3d85b1ebe5e3484250b6810f1a45c1ba5a4900f7 (diff)
downloadsamba-6dcbb84d485b8a8ccf0c3a70d9f5f7e951aaf1c6.tar.gz
samba-6dcbb84d485b8a8ccf0c3a70d9f5f7e951aaf1c6.tar.bz2
samba-6dcbb84d485b8a8ccf0c3a70d9f5f7e951aaf1c6.zip
Attempt to fix one of the last two bugs with the full Windows ACL support.
When returning an underlying ACL on a directory, normally on a POSIX system it has no inheritable entries, which breaks the Windows ACL when a user does a get/set of a Windows ACL on a POSIX directory with no existing stored Windows ACL from the Windows ACL editor. What happens is any new entry added by the user gets set inheritable, but none of the others entries are (as returned by default). So any new files then only inherit the single new ACE entry (the one marked inheritable by the ACL editor). Fix this by faking up a default 3 element inheritable ACL that represents what a user creating a POSIX file or directory will get by default from the smbd code. Jeremy.
Diffstat (limited to 'packaging4')
0 files changed, 0 insertions, 0 deletions