From d6c7e9b1ed6f7befbb2239350bba4547ef781e58 Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Mon, 12 Nov 2012 17:11:34 +1100 Subject: smbd: Remove NT4 compatability handling in posix -> NT ACL conversion NT4 is long dead, and we should not change which ACL we return based on what we think the client is. The reason we should not do this, is that if we are using vfs_acl_xattr then the hash will break if we do. Additionally, it would require that the python VFS interface set the global remote_arch to fake up being a modern client. This instead seems cleaner and removes untested code (the tests are updated to then handle the results of the modern codepath). The supporting 'acl compatability' parameter is also removed. Andrew Bartlett Reviewed by: Jeremy Allison --- docs-xml/smbdotconf/vfs/aclcompatibility.xml | 17 ----------------- 1 file changed, 17 deletions(-) delete mode 100644 docs-xml/smbdotconf/vfs/aclcompatibility.xml (limited to 'docs-xml/smbdotconf') diff --git a/docs-xml/smbdotconf/vfs/aclcompatibility.xml b/docs-xml/smbdotconf/vfs/aclcompatibility.xml deleted file mode 100644 index 95f42cfe2a..0000000000 --- a/docs-xml/smbdotconf/vfs/aclcompatibility.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - This parameter specifies what OS ACL semantics should - be compatible with. Possible values are winnt for Windows NT 4, - win2k for Windows 2000 and above and auto. - If you specify auto, the value for this parameter - will be based upon the version of the client. There should - be no reason to change this parameter from the default. - - -Auto -win2k - -- cgit