diff options
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/AccessControls.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/AccessControls.html | 212 |
1 files changed, 106 insertions, 106 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/AccessControls.html b/docs/htmldocs/Samba3-HOWTO/AccessControls.html index d53334a256..c4b5c0be40 100644 --- a/docs/htmldocs/Samba3-HOWTO/AccessControls.html +++ b/docs/htmldocs/Samba3-HOWTO/AccessControls.html @@ -1,6 +1,6 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 16. File, Directory, and Share Access Controls</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.1"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="rights.html" title="Chapter 15. User Rights and Privileges"><link rel="next" href="locking.html" title="Chapter 17. File and Record Locking"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 16. File, Directory, and Share Access Controls</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="rights.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="locking.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AccessControls"></a>Chapter 16. File, Directory, and Share Access Controls</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawing</span> <div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate">May 10, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="AccessControls.html#id2603577">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id2603772">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2603787">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2604122">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2604245">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2604911">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2604944">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2605310">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2605646">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2605983">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2606132">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2606478">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2606484">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2606531">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2606602">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2606745">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2606960">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2607117">Interaction with the Standard Samba “<span class="quote">create mask</span>” Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2607486">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2607559">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2607972">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2607983">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2608306">File Operations Done as <span class="emphasis"><em>root</em></span> with <span class="emphasis"><em>force user</em></span> Set</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2608351">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></div><p> -<a class="indexterm" name="id2603407"></a> -<a class="indexterm" name="id2603414"></a> +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 16. File, Directory, and Share Access Controls</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.1"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="rights.html" title="Chapter 15. User Rights and Privileges"><link rel="next" href="locking.html" title="Chapter 17. File and Record Locking"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 16. File, Directory, and Share Access Controls</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="rights.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="locking.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AccessControls"></a>Chapter 16. File, Directory, and Share Access Controls</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawing</span> <div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate">May 10, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="AccessControls.html#id2603577">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id2603772">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2603787">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2604123">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2604246">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2604911">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2604944">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2605311">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2605647">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2605984">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2606132">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2606479">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2606485">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2606532">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2606602">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2606746">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2606961">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2607118">Interaction with the Standard Samba “<span class="quote">create mask</span>” Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2607487">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2607560">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2607972">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2607984">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2608306">File Operations Done as <span class="emphasis"><em>root</em></span> with <span class="emphasis"><em>force user</em></span> Set</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2608352">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></div><p> +<a class="indexterm" name="id2603408"></a> +<a class="indexterm" name="id2603415"></a> <a class="indexterm" name="id2603421"></a> <a class="indexterm" name="id2603428"></a> Advanced MS Windows users are frequently perplexed when file, directory, and share manipulation of @@ -8,37 +8,37 @@ resources shared via Samba do not behave in the manner they might expect. MS Win administrators are often confused regarding network access controls and how to provide users with the access they need while protecting resources from unauthorized access. </p><p> -<a class="indexterm" name="id2603444"></a> -<a class="indexterm" name="id2603451"></a> +<a class="indexterm" name="id2603445"></a> +<a class="indexterm" name="id2603452"></a> Many UNIX administrators are unfamiliar with the MS Windows environment and in particular have difficulty in visualizing what the MS Windows user wishes to achieve in attempts to set file and directory access permissions. </p><p> <a class="indexterm" name="id2603466"></a> -<a class="indexterm" name="id2603472"></a> -<a class="indexterm" name="id2603479"></a> -<a class="indexterm" name="id2603486"></a> +<a class="indexterm" name="id2603473"></a> +<a class="indexterm" name="id2603480"></a> +<a class="indexterm" name="id2603487"></a> The problem lies in the differences in how file and directory permissions and controls work between the two environments. This difference is one that Samba cannot completely hide, even though it does try to bridge the chasm to a degree. </p><p> -<a class="indexterm" name="id2603499"></a> -<a class="indexterm" name="id2603506"></a> -<a class="indexterm" name="id2603515"></a> -<a class="indexterm" name="id2603522"></a> +<a class="indexterm" name="id2603500"></a> +<a class="indexterm" name="id2603507"></a> +<a class="indexterm" name="id2603516"></a> +<a class="indexterm" name="id2603523"></a> POSIX Access Control List technology has been available (along with extended attributes) for UNIX for many years, yet there is little evidence today of any significant use. This explains to some extent the slow adoption of ACLs into commercial Linux products. MS Windows administrators are astounded at this, given that ACLs were a foundational capability of the now decade-old MS Windows NT operating system. </p><p> -<a class="indexterm" name="id2603539"></a> +<a class="indexterm" name="id2603540"></a> The purpose of this chapter is to present each of the points of control that are possible with Samba-3 in the hope that this will help the network administrator to find the optimum method for delivering the best environment for MS Windows desktop users. </p><p> -<a class="indexterm" name="id2603554"></a> -<a class="indexterm" name="id2603561"></a> +<a class="indexterm" name="id2603555"></a> +<a class="indexterm" name="id2603562"></a> This is an opportune point to mention that Samba was created to provide a means of interoperability and interchange of data between differing operating environments. Samba has no intent to change UNIX/Linux into a platform like MS Windows. Instead the purpose was and is to provide a sufficient @@ -48,12 +48,12 @@ beyond early plans and expectations, yet the gap continues to shrink. Samba offers much flexibility in file system access management. These are the key access control facilities present in Samba today: </p><div class="itemizedlist"><p class="title"><b>Samba Access Control Facilities</b></p><ul type="disc"><li><p> - <a class="indexterm" name="id2603597"></a> + <a class="indexterm" name="id2603598"></a> <span class="emphasis"><em>UNIX File and Directory Permissions</em></span> </p><p> -<a class="indexterm" name="id2603614"></a> -<a class="indexterm" name="id2603621"></a> -<a class="indexterm" name="id2603628"></a> +<a class="indexterm" name="id2603615"></a> +<a class="indexterm" name="id2603622"></a> +<a class="indexterm" name="id2603629"></a> Samba honors and implements UNIX file system access controls. Users who access a Samba server will do so as a particular MS Windows user. This information is passed to the Samba server as part of the logon or @@ -64,7 +64,7 @@ beyond early plans and expectations, yet the gap continues to shrink. </p></li><li><p> <span class="emphasis"><em>Samba Share Definitions</em></span> </p><p> -<a class="indexterm" name="id2603665"></a> +<a class="indexterm" name="id2603666"></a> In configuring share settings and controls in the <code class="filename">smb.conf</code> file, the network administrator can exercise overrides to native file system permissions and behaviors. This can be handy and convenient @@ -75,7 +75,7 @@ beyond early plans and expectations, yet the gap continues to shrink. <span class="emphasis"><em>Samba Share ACLs</em></span> <a class="indexterm" name="id2603697"></a> </p><p> -<a class="indexterm" name="id2603709"></a> +<a class="indexterm" name="id2603710"></a> Just as it is possible in MS Windows NT to set ACLs on shares themselves, so it is possible to do in Samba. Few people make use of this facility, yet it remains one of the @@ -83,10 +83,10 @@ beyond early plans and expectations, yet the gap continues to shrink. do so with minimum invasiveness compared with other methods. </p></li><li><p> <a class="indexterm" name="id2603727"></a> - <a class="indexterm" name="id2603736"></a> + <a class="indexterm" name="id2603737"></a> <span class="emphasis"><em>MS Windows ACLs through UNIX POSIX ACLs</em></span> </p><p> -<a class="indexterm" name="id2603752"></a> +<a class="indexterm" name="id2603753"></a> The use of POSIX ACLs on UNIX/Linux is possible only if the underlying operating system supports them. If not, then this option will not be available to you. Current UNIX technology platforms have native support @@ -100,7 +100,7 @@ implement a totally divergent file system technology from what is provided in th environment. First we consider what the most significant differences are, then we look at how Samba helps to bridge the differences. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2603787"></a>MS Windows NTFS Comparison with UNIX File Systems</h3></div></div></div><p> - <a class="indexterm" name="id2603795"></a> + <a class="indexterm" name="id2603796"></a> <a class="indexterm" name="id2603802"></a> <a class="indexterm" name="id2603809"></a> <a class="indexterm" name="id2603818"></a> @@ -114,7 +114,7 @@ at how Samba helps to bridge the differences. but for the greater part we stay within the bounds of default behavior. Those wishing to explore the depths of control ability should review the <code class="filename">smb.conf</code> man page. </p><p>The following compares file system features for UNIX with those of MS Windows NT/200x: - <a class="indexterm" name="id2603853"></a> + <a class="indexterm" name="id2603854"></a> </p><div class="variablelist"><dl><dt><span class="term">Name Space</span></dt><dd><p> MS Windows NT4/200x/XP file names may be up to 254 characters long, and UNIX file names @@ -162,14 +162,14 @@ at how Samba helps to bridge the differences. The UNIX directory tree begins at <code class="constant">/</code> just as the root of a DOS drive is specified as <code class="constant">C:\</code>. </p></dd><dt><span class="term">File Naming Conventions</span></dt><dd><p> - <a class="indexterm" name="id2604033"></a> + <a class="indexterm" name="id2604034"></a> MS Windows generally never experiences file names that begin with a dot (<code class="constant">.</code>), while in UNIX these are commonly found in a user's home directory. Files that begin with a dot (<code class="constant">.</code>) are typically startup files for various UNIX applications, or they may be files that contain startup configuration data. </p></dd><dt><span class="term">Links and Short-Cuts</span></dt><dd><p> - <a class="indexterm" name="id2604063"></a> - <a class="indexterm" name="id2604072"></a> + <a class="indexterm" name="id2604064"></a> + <a class="indexterm" name="id2604073"></a> <a class="indexterm" name="id2604082"></a> MS Windows make use of <span class="emphasis"><em>links and shortcuts</em></span> that are actually special types of files that will redirect an attempt to execute the file to the real location of the file. UNIX knows of file and directory @@ -183,17 +183,17 @@ at how Samba helps to bridge the differences. There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort in the process of becoming familiar with UNIX/Linux. These are best left for a text that is dedicated to the purpose of UNIX/Linux training and education. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604122"></a>Managing Directories</h3></div></div></div><p> -<a class="indexterm" name="id2604130"></a> -<a class="indexterm" name="id2604137"></a> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604123"></a>Managing Directories</h3></div></div></div><p> +<a class="indexterm" name="id2604131"></a> +<a class="indexterm" name="id2604138"></a> <a class="indexterm" name="id2604144"></a> There are three basic operations for managing directories: <code class="literal">create</code>, <code class="literal">delete</code>, <code class="literal">rename</code>. <a class="link" href="AccessControls.html#TOSH-Accesstbl" title="Table 16.1. Managing Directories with UNIX and Windows">Managing Directories with UNIX and Windows</a> compares the commands in Windows and UNIX that implement these operations. - </p><div class="table"><a name="TOSH-Accesstbl"></a><p class="title"><b>Table 16.1. Managing Directories with UNIX and Windows</b></p><div class="table-contents"><table summary="Managing Directories with UNIX and Windows" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="center">Action</th><th align="center">MS Windows Command</th><th align="center">UNIX Command</th></tr></thead><tbody><tr><td align="center">create</td><td align="center">md folder</td><td align="center">mkdir folder</td></tr><tr><td align="center">delete</td><td align="center">rd folder</td><td align="center">rmdir folder</td></tr><tr><td align="center">rename</td><td align="center">rename oldname newname</td><td align="center">mv oldname newname</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604245"></a>File and Directory Access Control</h3></div></div></div><p> - <a class="indexterm" name="id2604253"></a> + </p><div class="table"><a name="TOSH-Accesstbl"></a><p class="title"><b>Table 16.1. Managing Directories with UNIX and Windows</b></p><div class="table-contents"><table summary="Managing Directories with UNIX and Windows" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="center">Action</th><th align="center">MS Windows Command</th><th align="center">UNIX Command</th></tr></thead><tbody><tr><td align="center">create</td><td align="center">md folder</td><td align="center">mkdir folder</td></tr><tr><td align="center">delete</td><td align="center">rd folder</td><td align="center">rmdir folder</td></tr><tr><td align="center">rename</td><td align="center">rename oldname newname</td><td align="center">mv oldname newname</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2604246"></a>File and Directory Access Control</h3></div></div></div><p> + <a class="indexterm" name="id2604254"></a> <a class="indexterm" name="id2604263"></a> -<a class="indexterm" name="id2604269"></a> +<a class="indexterm" name="id2604270"></a> The network administrator is strongly advised to read basic UNIX training manuals and reference materials regarding file and directory permissions maintenance. Much can be achieved with the basic UNIX permissions without having to resort to more complex facilities like POSIX ACLs or extended attributes (EAs). @@ -226,12 +226,12 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08 </p><div class="figure"><a name="access1"></a><p class="title"><b>Figure 16.1. Overview of UNIX permissions field.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/access1.png" width="216" alt="Overview of UNIX permissions field."></div></div></div><br class="figure-break"><p> Any bit flag may be unset. An unset bit flag is the equivalent of "cannot" and is represented as a “<span class="quote">-</span>” character (see <a class="link" href="AccessControls.html#access2" title="Example 16.1. Example File">“Example File”</a>) -<a class="indexterm" name="id2604411"></a> +<a class="indexterm" name="id2604412"></a> <a class="indexterm" name="id2604418"></a> <a class="indexterm" name="id2604425"></a> -<a class="indexterm" name="id2604431"></a> -<a class="indexterm" name="id2604438"></a> -<a class="indexterm" name="id2604445"></a> +<a class="indexterm" name="id2604432"></a> +<a class="indexterm" name="id2604439"></a> +<a class="indexterm" name="id2604446"></a> </p><div class="example"><a name="access2"></a><p class="title"><b>Example 16.1. Example File</b></p><div class="example-contents"><pre class="programlisting"> -rwxr-x--- Means: ^^^ The owner (user) can read, write, execute @@ -239,34 +239,34 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08 ^^^ everyone else cannot do anything with it. </pre></div></div><br class="example-break"><p> <a class="indexterm" name="id2604475"></a> -<a class="indexterm" name="id2604481"></a> -<a class="indexterm" name="id2604488"></a> -<a class="indexterm" name="id2604495"></a> +<a class="indexterm" name="id2604482"></a> +<a class="indexterm" name="id2604489"></a> +<a class="indexterm" name="id2604496"></a> Additional possibilities in the [type] field are c = character device, b = block device, p = pipe device, s = UNIX Domain Socket. </p><p> <a class="indexterm" name="id2604508"></a> -<a class="indexterm" name="id2604514"></a> -<a class="indexterm" name="id2604521"></a> -<a class="indexterm" name="id2604528"></a> -<a class="indexterm" name="id2604535"></a> +<a class="indexterm" name="id2604515"></a> +<a class="indexterm" name="id2604522"></a> +<a class="indexterm" name="id2604529"></a> +<a class="indexterm" name="id2604536"></a> The letters <code class="constant">rwxXst</code> set permissions for the user, group, and others as read (r), write (w), execute (or access for directories) (x), execute only if the file is a directory or already has execute permission for some user (X), set user (SUID) or group ID (SGID) on execution (s), sticky (t). </p><p> <a class="indexterm" name="id2604554"></a> -<a class="indexterm" name="id2604560"></a> -<a class="indexterm" name="id2604567"></a> -<a class="indexterm" name="id2604574"></a> +<a class="indexterm" name="id2604561"></a> +<a class="indexterm" name="id2604568"></a> +<a class="indexterm" name="id2604575"></a> When the sticky bit is set on a directory, files in that directory may be unlinked (deleted) or renamed only by root or their owner. Without the sticky bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on directories, such as <code class="filename">/tmp</code>, that are world-writable. </p><p> -<a class="indexterm" name="id2604595"></a> -<a class="indexterm" name="id2604602"></a> -<a class="indexterm" name="id2604609"></a> -<a class="indexterm" name="id2604616"></a> -<a class="indexterm" name="id2604625"></a> +<a class="indexterm" name="id2604596"></a> +<a class="indexterm" name="id2604603"></a> +<a class="indexterm" name="id2604610"></a> +<a class="indexterm" name="id2604617"></a> +<a class="indexterm" name="id2604626"></a> When the set user or group ID bit (s) is set on a directory, then all files created within it will be owned by the user and/or group whose `set user or group' bit is set. This can be helpful in setting up directories for which it is desired that all users who are in a group should be able to write to and read from a file, particularly when it is undesirable for that file @@ -276,11 +276,11 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08 the (r) read flags are not set, files cannot be listed (seen) in the directory by anyone. The group can read files in the directory but cannot create new files. If files in the directory are set to be readable and writable for the group, then group members will be able to write to (or delete) them. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2604657"></a>Protecting Directories and Files from Deletion</h4></div></div></div><p> + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2604658"></a>Protecting Directories and Files from Deletion</h4></div></div></div><p> <a class="indexterm" name="id2604666"></a> <a class="indexterm" name="id2604673"></a> <a class="indexterm" name="id2604680"></a> -<a class="indexterm" name="id2604686"></a> +<a class="indexterm" name="id2604687"></a> People have asked on the Samba mailing list how is it possible to protect files or directories from deletion by users. For example, Windows NT/2K/XP provides the capacity to set access controls on a directory into which people can write files but not delete them. It is possible to set an ACL on a Windows file that permits the file to be written to @@ -288,15 +288,15 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08 anyone who has the ability to create a file can write to it. Anyone who has write permission on the directory that contains a file and has write permission for it has the capability to delete it. </p><p> -<a class="indexterm" name="id2604708"></a> -<a class="indexterm" name="id2604715"></a> -<a class="indexterm" name="id2604722"></a> +<a class="indexterm" name="id2604709"></a> +<a class="indexterm" name="id2604716"></a> +<a class="indexterm" name="id2604723"></a> For the record, in the UNIX environment the ability to delete a file is controlled by the permissions on the directory that the file is in. In other words, a user can delete a file in a directory to which that user has write access, even if that user does not own the file. </p><p> -<a class="indexterm" name="id2604737"></a> -<a class="indexterm" name="id2604744"></a> +<a class="indexterm" name="id2604738"></a> +<a class="indexterm" name="id2604745"></a> <a class="indexterm" name="id2604751"></a> <a class="indexterm" name="id2604758"></a> Of necessity, Samba is subject to the file system semantics of the host operating system. Samba is therefore @@ -305,10 +305,10 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08 as extended attributes. Only the Windows concept of <span class="emphasis"><em>inheritance</em></span> is implemented by Samba through the appropriate extended attribute. </p><p> -<a class="indexterm" name="id2604779"></a> +<a class="indexterm" name="id2604780"></a> <a class="indexterm" name="id2604786"></a> <a class="indexterm" name="id2604793"></a> -<a class="indexterm" name="id2604799"></a> +<a class="indexterm" name="id2604800"></a> The specific semantics of the extended attributes are not consistent across UNIX and UNIX-like systems such as Linux. For example, it is possible on some implementations of the extended attributes to set a flag that prevents the directory or file from being deleted. The extended attribute that may achieve this is called the <code class="constant">immutible</code> bit. @@ -385,7 +385,7 @@ mystic:/home/hannibal > rm filename List of users that should be allowed to login to this service. </p></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#WRITELIST">write list</a></td><td align="justify"><p> List of users that are given read-write access to a service. - </p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605310"></a>File and Directory Permissions-Based Controls</h3></div></div></div><p> + </p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605311"></a>File and Directory Permissions-Based Controls</h3></div></div></div><p> Directory permission-based controls, if misused, can result in considerable difficulty in diagnosing the causes of misconfiguration. Use them sparingly and carefully. By gradually introducing each, one at a time, undesirable side effects may be detected. In the event of a problem, always comment all of them out and then gradually reintroduce @@ -416,7 +416,7 @@ mystic:/home/hannibal > rm filename This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT ACLs. </p></td></tr><tr><td align="left"><a class="link" href="smb.conf.5.html#SECURITYMASK">security mask</a></td><td align="justify"><p> Controls UNIX permission bits modified when a Windows NT client is manipulating the UNIX permissions on a file. - </p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605646"></a>Miscellaneous Controls</h3></div></div></div><p> + </p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2605647"></a>Miscellaneous Controls</h3></div></div></div><p> The parameters documented in <a class="link" href="AccessControls.html#mcoc" title="Table 16.4. Other Controls">Other Controls</a> are often used by administrators in ways that create inadvertent barriers to file access. Such are the consequences of not understanding the full implications of <code class="filename">smb.conf</code> file settings. @@ -449,30 +449,30 @@ mystic:/home/hannibal > rm filename If this parameter is yes, then users of a service may not create or modify files in the service's directory. </p></td></tr><tr><td align="justify"><a class="link" href="smb.conf.5.html#VETOFILES">veto files</a></td><td align="justify"><p> List of files and directories that are neither visible nor accessible. - </p></td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2605983"></a>Access Controls on Shares</h2></div></div></div><p> -<a class="indexterm" name="id2605991"></a> -<a class="indexterm" name="id2605998"></a> -<a class="indexterm" name="id2606005"></a> -<a class="indexterm" name="id2606012"></a> - <a class="indexterm" name="id2606019"></a> + </p></td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2605984"></a>Access Controls on Shares</h2></div></div></div><p> +<a class="indexterm" name="id2605992"></a> +<a class="indexterm" name="id2605999"></a> +<a class="indexterm" name="id2606006"></a> +<a class="indexterm" name="id2606013"></a> + <a class="indexterm" name="id2606020"></a> This section deals with how to configure Samba per-share access control restrictions. By default, Samba sets no restrictions on the share itself. Restrictions on the share itself can be set on MS Windows NT4/200x/XP shares. This can be an effective way to limit who can connect to a share. In the absence of specific restrictions, the default setting is to allow the global user <code class="constant">Everyone - Full Control</code> (full control, change and read). </p><p> -<a class="indexterm" name="id2606042"></a> -<a class="indexterm" name="id2606049"></a> -<a class="indexterm" name="id2606056"></a> +<a class="indexterm" name="id2606043"></a> +<a class="indexterm" name="id2606050"></a> +<a class="indexterm" name="id2606057"></a> At this time Samba does not provide a tool for configuring access control settings on the share itself the only way to create those settings is to use either the NT4 Server Manager or the Windows 200x Microsoft Management Console (MMC) for Computer Management. There are currently no plans to provide this capability in the Samba command-line tool set. </p><p> -<a class="indexterm" name="id2606072"></a> -<a class="indexterm" name="id2606079"></a> -<a class="indexterm" name="id2606086"></a> -<a class="indexterm" name="id2606093"></a> +<a class="indexterm" name="id2606073"></a> +<a class="indexterm" name="id2606080"></a> +<a class="indexterm" name="id2606087"></a> +<a class="indexterm" name="id2606094"></a> Samba stores the per-share access control settings in a file called <code class="filename">share_info.tdb</code>. The location of this file on your system will depend on how Samba was compiled. The default location for Samba's tdb files is under <code class="filename">/usr/local/samba/var</code>. If the <code class="filename">tdbdump</code> @@ -480,11 +480,11 @@ mystic:/home/hannibal > rm filename by executing <code class="literal">tdbdump share_info.tdb</code> in the directory containing the tdb files. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606132"></a>Share Permissions Management</h3></div></div></div><p> The best tool for share permissions management is platform-dependent. Choose the best tool for your environment. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606143"></a>Windows NT4 Workstation/Server</h4></div></div></div><p> -<a class="indexterm" name="id2606151"></a> -<a class="indexterm" name="id2606158"></a> -<a class="indexterm" name="id2606165"></a> -<a class="indexterm" name="id2606172"></a> + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606144"></a>Windows NT4 Workstation/Server</h4></div></div></div><p> +<a class="indexterm" name="id2606152"></a> +<a class="indexterm" name="id2606159"></a> +<a class="indexterm" name="id2606166"></a> +<a class="indexterm" name="id2606173"></a> The tool you need to manage share permissions on a Samba server from a Windows NT4 Workstation or Server is the NT Server Manager. Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. You can obtain the NT Server Manager for MS Windows NT4 Workstation from the Microsoft @@ -496,9 +496,9 @@ mystic:/home/hannibal > rm filename </p></li><li><p> Click on the share that you wish to manage and click the <span class="guilabel">Properties</span> tab, then click the <span class="guilabel">Permissions</span> tab. Now you can add or change access control settings as you wish. - </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606248"></a>Windows 200x/XP</h4></div></div></div><p> -<a class="indexterm" name="id2606256"></a> -<a class="indexterm" name="id2606263"></a> + </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606249"></a>Windows 200x/XP</h4></div></div></div><p> +<a class="indexterm" name="id2606257"></a> +<a class="indexterm" name="id2606264"></a> <a class="indexterm" name="id2606270"></a> <a class="indexterm" name="id2606277"></a> On <span class="application">MS Windows NT4/200x/XP</span> systems, ACLs on the share itself are set using @@ -506,9 +506,9 @@ mystic:/home/hannibal > rm filename then select <span class="guimenuitem">Sharing</span>, then click on <span class="guilabel">Permissions</span>. The default Windows NT4/200x permissions allow the group "Everyone" full control on the share. </p><p> -<a class="indexterm" name="id2606309"></a> -<a class="indexterm" name="id2606316"></a> -<a class="indexterm" name="id2606323"></a> +<a class="indexterm" name="id2606310"></a> +<a class="indexterm" name="id2606317"></a> +<a class="indexterm" name="id2606324"></a> MS Windows 200x and later versions come with a tool called the <span class="application">Computer Management</span> snap-in for the MMC. This tool can be accessed via <span class="guimenu">Control Panel -> Administrative Tools -> Computer Management</span>. @@ -534,7 +534,7 @@ mystic:/home/hannibal > rm filename ACL precedence. Everyone with <span class="emphasis"><em>no access</em></span> means that <code class="constant">MaryK</code> who is part of the group <code class="constant">Everyone</code> will have no access even if she is given explicit full control access. - </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2606478"></a>MS Windows Access Control Lists and UNIX Interoperability</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606484"></a>Managing UNIX Permissions Using NT Security Dialogs</h3></div></div></div><p> + </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2606479"></a>MS Windows Access Control Lists and UNIX Interoperability</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606485"></a>Managing UNIX Permissions Using NT Security Dialogs</h3></div></div></div><p> <a class="indexterm" name="id2606493"></a> Windows NT clients can use their native security settings dialog box to view and modify the underlying UNIX permissions. @@ -549,7 +549,7 @@ mystic:/home/hannibal > rm filename When trying to figure out file access problems, it is vitally important to find the identity of the Windows user as it is presented by Samba at the point of file access. This can best be determined from the Samba log files. - </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606531"></a>Viewing File Security on a Samba Share</h3></div></div></div><p> + </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606532"></a>Viewing File Security on a Samba Share</h3></div></div></div><p> From an NT4/2000/XP client, right-click on any file or directory in a Samba-mounted drive letter or UNC path. When the menu pops up, click on the <span class="guilabel">Properties</span> entry at the bottom of the menu. This brings up the file <code class="constant">Properties</code> dialog box. Click on the @@ -582,14 +582,14 @@ mystic:/home/hannibal > rm filename NT to attempt to change the ownership of a file to the current user logged into the NT client, this will not work with Samba at this time. </p><p> -<a class="indexterm" name="id2606704"></a> -<a class="indexterm" name="id2606711"></a> -<a class="indexterm" name="id2606718"></a> +<a class="indexterm" name="id2606705"></a> +<a class="indexterm" name="id2606712"></a> +<a class="indexterm" name="id2606719"></a> There is an NT <code class="literal">chown</code> command that will work with Samba and allow a user with administrator privilege connected to a Samba server as root to change the ownership of files on both a local NTFS file system or remote mounted NTFS or Samba drive. This is available as part of the <span class="application">Seclib</span> NT security library written by Jeremy Allison of the Samba Team and is downloadable from the main Samba FTP site. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606745"></a>Viewing File or Directory Permissions</h3></div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606746"></a>Viewing File or Directory Permissions</h3></div></div></div><p> The third button is the <span class="guibutton">Permissions</span> button. Clicking on it brings up a dialog box that shows both the permissions and the UNIX owner of the file or directory. The owner is displayed like this: </p><p><code class="literal"><em class="replaceable"><code>SERVER</code></em>\ @@ -603,7 +603,7 @@ mystic:/home/hannibal > rm filename shown as NT <span class="emphasis"><em>Full Control</em></span>. </p><p> The permissions field is displayed differently for files and directories. Both are discussed next. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606828"></a>File Permissions</h4></div></div></div><p> + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606829"></a>File Permissions</h4></div></div></div><p> The standard UNIX user/group/world triplet and the corresponding <code class="constant">read, write, execute</code> permissions triplets are mapped by Samba into a three-element NT ACL with the “<span class="quote">r</span>”, “<span class="quote">w</span>”, and “<span class="quote">x</span>” bits mapped into the corresponding NT @@ -621,7 +621,7 @@ mystic:/home/hannibal > rm filename <code class="constant">Take Ownership</code> ACL attribute (which has no meaning in UNIX) and reports a component with no permissions as having the NT <code class="literal">O</code> bit set. This was chosen, of course, to make it look like a zero, meaning zero permissions. More details on the decision behind this action are given below. - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606922"></a>Directory Permissions</h4></div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2606923"></a>Directory Permissions</h4></div></div></div><p> Directories on an NT NTFS file system have two different sets of permissions. The first set is the ACL set on the directory itself, which is usually displayed in the first set of parentheses in the normal <code class="constant">RW</code> NT style. This first set of permissions is created by Samba in exactly the same way as normal file permissions are, described @@ -632,7 +632,7 @@ mystic:/home/hannibal > rm filename </p><p> Samba synthesizes these inherited permissions for NT by returning as an NT ACL the UNIX permission mode that a new file created by Samba on this share would receive. - </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606960"></a>Modifying File or Directory Permissions</h3></div></div></div><p> + </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2606961"></a>Modifying File or Directory Permissions</h3></div></div></div><p> Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box and clicking on <span class="guibutton">OK</span>. However, there are limitations that a user needs to be aware of, and also interactions with the standard Samba permission masks and mapping of DOS attributes that also need to @@ -665,7 +665,7 @@ mystic:/home/hannibal > rm filename If you wish to remove all permissions from a user/group/world component, you may either highlight the component and click on the <span class="guibutton">Remove</span> button or set the component to only have the special <code class="constant">Take Ownership</code> permission (displayed as <code class="literal">O</code>) highlighted. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607117"></a>Interaction with the Standard Samba “<span class="quote">create mask</span>” Parameters</h3></div></div></div><p>There are four parameters that control interaction with the standard Samba <em class="parameter"><code>create mask</code></em> parameters: + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607118"></a>Interaction with the Standard Samba “<span class="quote">create mask</span>” Parameters</h3></div></div></div><p>There are four parameters that control interaction with the standard Samba <em class="parameter"><code>create mask</code></em> parameters: </p><div class="itemizedlist"><ul type="disc"><li><p><a class="link" href="smb.conf.5.html#SECURITYMASK">security mask</a></p></li><li><p><a class="link" href="smb.conf.5.html#FORCESECURITYMODE">force security mode</a></p></li><li><p><a class="link" href="smb.conf.5.html#DIRECTORYSECURITYMASK">directory security mask</a></p></li><li><p><a class="link" href="smb.conf.5.html#FORCEDIRECTORYSECURITYMODE">force directory security mode</a></p></li></ul></div><p> @@ -719,7 +719,7 @@ mystic:/home/hannibal > rm filename does not force any particular bits to be set <span class="emphasis"><em>on</em></span>, then set the following parameters in the <code class="filename">smb.conf</code> file in that share-specific section: - </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2607438"></a><em class="parameter"><code>security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2607449"></a><em class="parameter"><code>force security mode = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2607461"></a><em class="parameter"><code>directory security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2607473"></a><em class="parameter"><code>force directory security mode = 0</code></em></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607486"></a>Interaction with the Standard Samba File Attribute Mapping</h3></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2607438"></a><em class="parameter"><code>security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2607450"></a><em class="parameter"><code>force security mode = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2607461"></a><em class="parameter"><code>directory security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2607474"></a><em class="parameter"><code>force directory security mode = 0</code></em></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607487"></a>Interaction with the Standard Samba File Attribute Mapping</h3></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Samba maps some of the DOS attribute bits (such as “<span class="quote">read-only</span>”) into the UNIX permissions of a file. This means there can be a conflict between the permission bits set via the security @@ -740,7 +740,7 @@ mystic:/home/hannibal > rm filename attributes dialog, you should always press <span class="guibutton">Cancel</span> rather than <span class="guibutton">OK</span> to ensure that your changes are not overridden. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607559"></a>Windows NT/200X ACLs and POSIX ACLs Limitations</h3></div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607560"></a>Windows NT/200X ACLs and POSIX ACLs Limitations</h3></div></div></div><p> Windows administrators are familiar with simple ACL controls, and they typically consider that UNIX user/group/other (ugo) permissions are inadequate and not sufficiently fine-grained. @@ -768,7 +768,7 @@ mystic:/home/hannibal > rm filename ACLs as implemented in UNIX file systems. Samba provides support for <span class="emphasis"><em>masks</em></span> that permit normal ugo and ACLs functionality to be overrided. This further complicates the way in which Windows ACLs must be implemented. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2607617"></a>UNIX POSIX ACL Overview</h4></div></div></div><p> + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2607618"></a>UNIX POSIX ACL Overview</h4></div></div></div><p> In examining POSIX ACLs we must consider the manner in which they operate for both files and directories. File ACLs have the following significance: </p><pre class="screen"> @@ -797,7 +797,7 @@ default:group::r-x <-- inherited group perms default:mask:rwx <-- inherited default mask default:other:--- <-- inherited permissions for everyone (other) </pre><p> - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2607678"></a>Mapping of Windows File ACLs to UNIX POSIX ACLs</h4></div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2607679"></a>Mapping of Windows File ACLs to UNIX POSIX ACLs</h4></div></div></div><p> Microsoft Windows NT4/200X ACLs must of necessity be mapped to POSIX ACLs. The mappings for file permissions are shown in <a class="link" href="AccessControls.html#fdsacls" title="Table 16.5. How Windows File ACLs Map to UNIX POSIX File ACLs">How Windows File ACLs Map to UNIX POSIX File ACLs</a>. @@ -816,7 +816,7 @@ default:other:--- <-- inherited permissions for everyone (other) The UNIX administrator can set any directory permission from within the UNIX environment. The Windows administrator is more restricted in that it is not possible from within Windows Explorer to remove read permission for the file owner. - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2607947"></a>Mapping of Windows Directory ACLs to UNIX POSIX ACLs</h4></div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2607948"></a>Mapping of Windows Directory ACLs to UNIX POSIX ACLs</h4></div></div></div><p> Interesting things happen in the mapping of UNIX POSIX directory permissions and UNIX POSIX ACLs to Windows ACEs (Access Control Entries, the discrete components of an ACL) are mapped to Windows directory ACLs. @@ -827,7 +827,7 @@ default:other:--- <-- inherited permissions for everyone (other) </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2607972"></a>Common Errors</h2></div></div></div><p> File, directory, and share access problems are common topics on the mailing list. The following are examples recently taken from the mailing list. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607983"></a>Users Cannot Write to a Public Share</h3></div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2607984"></a>Users Cannot Write to a Public Share</h3></div></div></div><p> The following complaint has frequently been voiced on the Samba mailing list: “<span class="quote"> We are facing some troubles with file/directory permissions. I can log on the domain as admin user (root), @@ -891,7 +891,7 @@ drwxrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2608306"></a>File Operations Done as <span class="emphasis"><em>root</em></span> with <span class="emphasis"><em>force user</em></span> Set</h3></div></div></div><p> When you have a user in <a class="link" href="smb.conf.5.html#ADMINUSERS">admin users</a>, Samba will always do file operations for this user as <span class="emphasis"><em>root</em></span>, even if <a class="link" href="smb.conf.5.html#FORCEUSER">force user</a> has been set. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2608351"></a>MS Word with Samba Changes Owner of File</h3></div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2608352"></a>MS Word with Samba Changes Owner of File</h3></div></div></div><p> <span class="emphasis"><em>Question:</em></span> “<span class="quote">When user B saves a word document that is owned by user A, the updated file is now owned by user B. Why is Samba doing this? How do I fix this?</span>” </p><p> @@ -906,7 +906,7 @@ drwxrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar in which you are changing Word documents: <code class="literal">chmod g+s `directory_name'.</code> This ensures that all files will be created with the group that owns the directory. In <code class="filename">smb.conf</code> share declaration section set: </p><p> - </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2608420"></a><em class="parameter"><code>force create mode = 0660</code></em></td></tr><tr><td><a class="indexterm" name="id2608432"></a><em class="parameter"><code>force directory mode = 0770</code></em></td></tr></table><p> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2608421"></a><em class="parameter"><code>force create mode = 0660</code></em></td></tr><tr><td><a class="indexterm" name="id2608433"></a><em class="parameter"><code>force directory mode = 0770</code></em></td></tr></table><p> </p><p> These two settings will ensure that all directories and files that get created in the share will be readable/writable by the owner and group set on the directory itself. |