diff options
| author | Andrew Bartlett <abartlet@samba.org> | 2012-11-12 17:11:34 +1100 |
|---|---|---|
| committer | Andrew Bartlett <abartlet@samba.org> | 2012-11-13 22:48:19 +0100 |
| commit | d6c7e9b1ed6f7befbb2239350bba4547ef781e58 (patch) | |
| tree | ff40ee12b658dbae88128852588f82b74d6f958d /docs-xml/smbdotconf/vfs | |
| parent | 236977bf4642c035bb22cfcd1cee481c5f6c6da1 (diff) | |
| download | samba-d6c7e9b1ed6f7befbb2239350bba4547ef781e58.tar.gz samba-d6c7e9b1ed6f7befbb2239350bba4547ef781e58.tar.bz2 samba-d6c7e9b1ed6f7befbb2239350bba4547ef781e58.zip | |
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 <jra@samba.org>
Diffstat (limited to 'docs-xml/smbdotconf/vfs')
| -rw-r--r-- | docs-xml/smbdotconf/vfs/aclcompatibility.xml | 17 |
1 files changed, 0 insertions, 17 deletions
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 @@ -<samba:parameter name="acl compatibility" - context="G" - type="enum" - advanced="1" developer="1" - xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> -<description> - <para>This parameter specifies what OS ACL semantics should - be compatible with. Possible values are <emphasis>winnt</emphasis> for Windows NT 4, - <emphasis>win2k</emphasis> for Windows 2000 and above and <emphasis>auto</emphasis>. - If you specify <emphasis>auto</emphasis>, 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.</para> -</description> - -<value type="default">Auto</value> -<value type="example">win2k</value> -</samba:parameter> |