diff options
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/AccessControls.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/AccessControls.html | 364 |
1 files changed, 182 insertions, 182 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/AccessControls.html b/docs/htmldocs/Samba3-HOWTO/AccessControls.html index 92313a7623..da33a6eceb 100644 --- a/docs/htmldocs/Samba3-HOWTO/AccessControls.html +++ b/docs/htmldocs/Samba3-HOWTO/AccessControls.html @@ -1,59 +1,59 @@ -<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.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.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="orgname">Samba Team</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="orgname">Samba Team</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="orgname">The Samba Team</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#id2610562">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id2610748">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2610763">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611105">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2611229">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2611888">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2611921">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612289">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2612626">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2612964">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613112">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2613459">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2613465">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613512">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613583">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613726">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2613942">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614099">Interaction with the Standard Samba create mask Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614468">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2614541">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id2614954">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id2614965">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615288">File Operations Done as root with force user Set</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id2615334">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></div><p> -<a class="indexterm" name="id2610392"></a> -<a class="indexterm" name="id2610399"></a> -<a class="indexterm" name="id2610406"></a> -<a class="indexterm" name="id2610413"></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.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.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" title="Chapter 16. File, Directory, and Share Access Controls"><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#id378519">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="AccessControls.html#id378687">File System Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id378699">MS Windows NTFS Comparison with UNIX File Systems</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id379000">Managing Directories</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id379121">File and Directory Access Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id379717">Share Definition Access Controls</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id379748">User- and Group-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id380091">File and Directory Permissions-Based Controls</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id380402">Miscellaneous Controls</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id380718">Access Controls on Shares</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id380854">Share Permissions Management</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id381176">MS Windows Access Control Lists and UNIX Interoperability</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id381182">Managing UNIX Permissions Using NT Security Dialogs</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id381222">Viewing File Security on a Samba Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id381286">Viewing File Ownership</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id381416">Viewing File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id381607">Modifying File or Directory Permissions</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id381747">Interaction with the Standard Samba <span class="quote">“<span class="quote">create mask</span>”</span> Parameters</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id382083">Interaction with the Standard Samba File Attribute Mapping</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id382146">Windows NT/200X ACLs and POSIX ACLs Limitations</a></span></dt></dl></dd><dt><span class="sect1"><a href="AccessControls.html#id382508">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="AccessControls.html#id382518">Users Cannot Write to a Public Share</a></span></dt><dt><span class="sect2"><a href="AccessControls.html#id382825">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#id382869">MS Word with Samba Changes Owner of File</a></span></dt></dl></dd></dl></div><p> +<a class="indexterm" name="id378368"></a> +<a class="indexterm" name="id378374"></a> +<a class="indexterm" name="id378381"></a> +<a class="indexterm" name="id378388"></a> Advanced MS Windows users are frequently perplexed when file, directory, and share manipulation of resources shared via Samba do not behave in the manner they might expect. MS Windows network 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="id2610429"></a> -<a class="indexterm" name="id2610436"></a> +<a class="indexterm" name="id378401"></a> +<a class="indexterm" name="id378408"></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="id2610451"></a> -<a class="indexterm" name="id2610457"></a> -<a class="indexterm" name="id2610464"></a> -<a class="indexterm" name="id2610471"></a> +<a class="indexterm" name="id378420"></a> +<a class="indexterm" name="id378427"></a> +<a class="indexterm" name="id378434"></a> +<a class="indexterm" name="id378440"></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="id2610484"></a> -<a class="indexterm" name="id2610491"></a> -<a class="indexterm" name="id2610500"></a> -<a class="indexterm" name="id2610507"></a> +<a class="indexterm" name="id378451"></a> +<a class="indexterm" name="id378458"></a> +<a class="indexterm" name="id378467"></a> +<a class="indexterm" name="id378474"></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="id2610524"></a> +<a class="indexterm" name="id378488"></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="id2610539"></a> -<a class="indexterm" name="id2610546"></a> +<a class="indexterm" name="id378500"></a> +<a class="indexterm" name="id378507"></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 level of exchange of data between the two environments. What is available today extends well beyond early plans and expectations, yet the gap continues to shrink. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2610562"></a>Features and Benefits</h2></div></div></div><p> +</p><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id378519"></a>Features and Benefits</h2></div></div></div><p> 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="id2610582"></a> + </p><div class="itemizedlist" title="Samba Access Control Facilities"><p class="title"><b>Samba Access Control Facilities</b></p><ul class="itemizedlist" type="disc"><li class="listitem"><p> + <a class="indexterm" name="id378538"></a> <span class="emphasis"><em>UNIX File and Directory Permissions</em></span> </p><p> -<a class="indexterm" name="id2610599"></a> -<a class="indexterm" name="id2610606"></a> -<a class="indexterm" name="id2610613"></a> +<a class="indexterm" name="id378554"></a> +<a class="indexterm" name="id378561"></a> +<a class="indexterm" name="id378568"></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 @@ -61,32 +61,32 @@ beyond early plans and expectations, yet the gap continues to shrink. whether or not the user should be given access to file system resources (files and directories). This chapter provides an overview for those to whom the UNIX permissions and controls are a little strange or unknown. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>Samba Share Definitions</em></span> </p><p> -<a class="indexterm" name="id2610641"></a> +<a class="indexterm" name="id378591"></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 to effect behavior that is more like what MS Windows NT users expect, but it is seldom the <span class="emphasis"><em>best</em></span> way to achieve this. The basic options and techniques are described herein. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>Samba Share ACLs</em></span> - <a class="indexterm" name="id2610673"></a> + <a class="indexterm" name="id378619"></a> </p><p> -<a class="indexterm" name="id2610685"></a> +<a class="indexterm" name="id378632"></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 easiest ways to affect access controls (restrictions) and can often do so with minimum invasiveness compared with other methods. - </p></li><li><p> - <a class="indexterm" name="id2610703"></a> - <a class="indexterm" name="id2610712"></a> + </p></li><li class="listitem"><p> + <a class="indexterm" name="id378646"></a> + <a class="indexterm" name="id378656"></a> <span class="emphasis"><em>MS Windows ACLs through UNIX POSIX ACLs</em></span> </p><p> -<a class="indexterm" name="id2610729"></a> +<a class="indexterm" name="id378672"></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 @@ -94,16 +94,16 @@ beyond early plans and expectations, yet the gap continues to shrink. this support. Sadly, few Linux platforms ship today with native ACLs and extended attributes enabled. This chapter has pertinent information for users of platforms that support them. - </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2610748"></a>File System Access Controls</h2></div></div></div><p> + </p></li></ul></div></div><div class="sect1" title="File System Access Controls"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id378687"></a>File System Access Controls</h2></div></div></div><p> Perhaps the most important recognition to be made is the simple fact that MS Windows NT4/200x/XP implement a totally divergent file system technology from what is provided in the UNIX operating system 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="id2610763"></a>MS Windows NTFS Comparison with UNIX File Systems</h3></div></div></div><p> - <a class="indexterm" name="id2610771"></a> - <a class="indexterm" name="id2610778"></a> - <a class="indexterm" name="id2610785"></a> - <a class="indexterm" name="id2610794"></a> +</p><div class="sect2" title="MS Windows NTFS Comparison with UNIX File Systems"><div class="titlepage"><div><div><h3 class="title"><a name="id378699"></a>MS Windows NTFS Comparison with UNIX File Systems</h3></div></div></div><p> + <a class="indexterm" name="id378707"></a> + <a class="indexterm" name="id378714"></a> + <a class="indexterm" name="id378720"></a> + <a class="indexterm" name="id378730"></a> Samba operates on top of the UNIX file system. This means it is subject to UNIX file system conventions and permissions. It also means that if the MS Windows networking environment requires file system behavior, that differs from UNIX file system behavior then somehow Samba is responsible for emulating @@ -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="id2610835"></a> + <a class="indexterm" name="id378761"></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 @@ -123,8 +123,8 @@ at how Samba helps to bridge the differences. </p><p> What MS Windows calls a folder, UNIX calls a directory. </p></dd><dt><span class="term">Case Sensitivity</span></dt><dd><p> - <a class="indexterm" name="id2610880"></a> - <a class="indexterm" name="id2610887"></a> + <a class="indexterm" name="id378803"></a> + <a class="indexterm" name="id378810"></a> MS Windows file names are generally uppercase if made up of 8.3 (8-character file name and 3 character extension. File names that are longer than 8.3 are case preserving and case insensitive. @@ -151,49 +151,49 @@ at how Samba helps to bridge the differences. event that the UNIX directory contains multiple files that would match a case insensitive file listing. </p></dd><dt><span class="term">Directory Separators</span></dt><dd><p> - <a class="indexterm" name="id2610951"></a> + <a class="indexterm" name="id378863"></a> MS Windows and DOS use the backslash <code class="constant">\</code> as a directory delimiter, and UNIX uses the forward-slash <code class="constant">/</code> as its directory delimiter. This is handled transparently by Samba. </p></dd><dt><span class="term">Drive Identification</span></dt><dd><p> - <a class="indexterm" name="id2610979"></a> + <a class="indexterm" name="id378888"></a> MS Windows products support a notion of drive letters, like <code class="literal">C:</code>, to represent disk partitions. UNIX has no concept of separate identifiers for file partitions; each such file system is mounted to become part of the overall directory tree. 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="id2611016"></a> + <a class="indexterm" name="id378922"></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="id2611046"></a> - <a class="indexterm" name="id2611056"></a> - <a class="indexterm" name="id2611065"></a> + <a class="indexterm" name="id378949"></a> + <a class="indexterm" name="id378958"></a> + <a class="indexterm" name="id378967"></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 links, but they are entirely different from what MS Windows users are used to. </p><p> Symbolic links are files in UNIX that contain the actual location of the data (file or directory). An operation (like read or write) will operate directly on the file referenced. Symbolic links are also - referred to as “<span class="quote">soft links.</span>” A hard link is something that MS Windows is not familiar with. It allows + referred to as <span class="quote">“<span class="quote">soft links.</span>”</span> A hard link is something that MS Windows is not familiar with. It allows one physical file to be known simultaneously by more than one file name. </p></dd></dl></div><p> 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="id2611105"></a>Managing Directories</h3></div></div></div><p> -<a class="indexterm" name="id2611113"></a> -<a class="indexterm" name="id2611120"></a> -<a class="indexterm" name="id2611127"></a> + </p></div><div class="sect2" title="Managing Directories"><div class="titlepage"><div><div><h3 class="title"><a name="id379000"></a>Managing Directories</h3></div></div></div><p> +<a class="indexterm" name="id379007"></a> +<a class="indexterm" name="id379014"></a> +<a class="indexterm" name="id379021"></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="id2611229"></a>File and Directory Access Control</h3></div></div></div><p> - <a class="indexterm" name="id2611237"></a> -<a class="indexterm" name="id2611246"></a> -<a class="indexterm" name="id2611253"></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" title="File and Directory Access Control"><div class="titlepage"><div><div><h3 class="title"><a name="id379121"></a>File and Directory Access Control</h3></div></div></div><p> + <a class="indexterm" name="id379129"></a> +<a class="indexterm" name="id379138"></a> +<a class="indexterm" name="id379145"></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). @@ -225,48 +225,48 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08 field</a>. </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="id2611381"></a> -<a class="indexterm" name="id2611388"></a> -<a class="indexterm" name="id2611395"></a> -<a class="indexterm" name="id2611402"></a> -<a class="indexterm" name="id2611408"></a> -<a class="indexterm" name="id2611415"></a> + as a <span class="quote">“<span class="quote">-</span>”</span> character (see <a class="link" href="AccessControls.html#access2" title="Example 16.1. Example File">“Example File”</a>) +<a class="indexterm" name="id379258"></a> +<a class="indexterm" name="id379265"></a> +<a class="indexterm" name="id379272"></a> +<a class="indexterm" name="id379279"></a> +<a class="indexterm" name="id379285"></a> +<a class="indexterm" name="id379292"></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 ^^^ the group can read and execute ^^^ everyone else cannot do anything with it. </pre></div></div><br class="example-break"><p> -<a class="indexterm" name="id2611445"></a> -<a class="indexterm" name="id2611452"></a> -<a class="indexterm" name="id2611458"></a> -<a class="indexterm" name="id2611465"></a> +<a class="indexterm" name="id379320"></a> +<a class="indexterm" name="id379326"></a> +<a class="indexterm" name="id379333"></a> +<a class="indexterm" name="id379340"></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="id2611478"></a> -<a class="indexterm" name="id2611485"></a> -<a class="indexterm" name="id2611491"></a> -<a class="indexterm" name="id2611498"></a> -<a class="indexterm" name="id2611505"></a> +<a class="indexterm" name="id379351"></a> +<a class="indexterm" name="id379358"></a> +<a class="indexterm" name="id379365"></a> +<a class="indexterm" name="id379372"></a> +<a class="indexterm" name="id379378"></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="id2611524"></a> -<a class="indexterm" name="id2611530"></a> -<a class="indexterm" name="id2611537"></a> -<a class="indexterm" name="id2611544"></a> +<a class="indexterm" name="id379395"></a> +<a class="indexterm" name="id379402"></a> +<a class="indexterm" name="id379408"></a> +<a class="indexterm" name="id379415"></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="id2611566"></a> -<a class="indexterm" name="id2611572"></a> -<a class="indexterm" name="id2611579"></a> -<a class="indexterm" name="id2611586"></a> -<a class="indexterm" name="id2611595"></a> +<a class="indexterm" name="id379434"></a> +<a class="indexterm" name="id379441"></a> +<a class="indexterm" name="id379447"></a> +<a class="indexterm" name="id379454"></a> +<a class="indexterm" name="id379463"></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="id2611627"></a>Protecting Directories and Files from Deletion</h4></div></div></div><p> -<a class="indexterm" name="id2611636"></a> -<a class="indexterm" name="id2611643"></a> -<a class="indexterm" name="id2611650"></a> -<a class="indexterm" name="id2611657"></a> + </p><div class="sect3" title="Protecting Directories and Files from Deletion"><div class="titlepage"><div><div><h4 class="title"><a name="id379488"></a>Protecting Directories and Files from Deletion</h4></div></div></div><p> +<a class="indexterm" name="id379496"></a> +<a class="indexterm" name="id379503"></a> +<a class="indexterm" name="id379510"></a> +<a class="indexterm" name="id379516"></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,27 +288,27 @@ 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="id2611678"></a> -<a class="indexterm" name="id2611685"></a> -<a class="indexterm" name="id2611692"></a> +<a class="indexterm" name="id379532"></a> +<a class="indexterm" name="id379539"></a> +<a class="indexterm" name="id379546"></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="id2611707"></a> -<a class="indexterm" name="id2611714"></a> -<a class="indexterm" name="id2611721"></a> -<a class="indexterm" name="id2611728"></a> +<a class="indexterm" name="id379558"></a> +<a class="indexterm" name="id379565"></a> +<a class="indexterm" name="id379572"></a> +<a class="indexterm" name="id379579"></a> Of necessity, Samba is subject to the file system semantics of the host operating system. Samba is therefore limited in the file system capabilities that can be made available through Windows ACLs, and therefore performs a "best fit" translation to POSIX ACLs. Some UNIX file systems do, however support, a feature known 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="id2611756"></a> -<a class="indexterm" name="id2611763"></a> -<a class="indexterm" name="id2611770"></a> -<a class="indexterm" name="id2611776"></a> +<a class="indexterm" name="id379600"></a> +<a class="indexterm" name="id379606"></a> +<a class="indexterm" name="id379613"></a> +<a class="indexterm" name="id379620"></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. @@ -322,14 +322,14 @@ CAP_LINUX_IMMUTABLE capability can set or clear this attribute. </pre><p> A simple test can be done to check if the immutible flag is supported on files in the file system of the Samba host server. - </p><div class="procedure"><a name="id2611815"></a><p class="title"><b>Procedure 16.1. Test for File Immutibility Support</b></p><ol type="1"><li><p> + </p><div class="procedure" title="Procedure 16.1. Test for File Immutibility Support"><a name="id379651"></a><p class="title"><b>Procedure 16.1. Test for File Immutibility Support</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> Create a file called <code class="filename">filename</code>. - </p></li><li><p> + </p></li><li class="step" title="Step 2"><p> Login as the <code class="constant">root</code> user, then set the immutibile flag on a test file as follows: </p><pre class="screen"> <code class="prompt">root# </code> chattr +i `filename' </pre><p> - </p></li><li><p> + </p></li><li class="step" title="Step 3"><p> Login as the user who owns the file (not root) and attempt to remove the file as follows: </p><pre class="screen"> mystic:/home/hannibal > rm filename @@ -340,11 +340,11 @@ mystic:/home/hannibal > rm filename that cannot be deleted. Check the man page on your particular host system to determine whether or not immutable directories are writable. If they are not, then the entire directory and its contents will effectively be protected from writing (file creation also) and deletion. - </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2611888"></a>Share Definition Access Controls</h2></div></div></div><p> - <a class="indexterm" name="id2611896"></a> + </p></div></div></div><div class="sect1" title="Share Definition Access Controls"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id379717"></a>Share Definition Access Controls</h2></div></div></div><p> + <a class="indexterm" name="id379725"></a> The following parameters in the <code class="filename">smb.conf</code> file sections define a share control or affect access controls. Before using any of the following options, please refer to the man page for <code class="filename">smb.conf</code>. - </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2611921"></a>User- and Group-Based Controls</h3></div></div></div><p> + </p><div class="sect2" title="User- and Group-Based Controls"><div class="titlepage"><div><div><h3 class="title"><a name="id379748"></a>User- and Group-Based Controls</h3></div></div></div><p> User- and group-based controls can prove quite useful. In some situations it is distinctly desirable to force all file system operations as if a single user were doing so. The use of the <a class="link" href="smb.conf.5.html#FORCEUSER" target="_top">force user</a> and <a class="link" href="smb.conf.5.html#FORCEGROUP" target="_top">force group</a> behavior will achieve this. @@ -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" target="_top">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="id2612289"></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" title="File and Directory Permissions-Based Controls"><div class="titlepage"><div><div><h3 class="title"><a name="id380091"></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" target="_top">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="id2612626"></a>Miscellaneous Controls</h3></div></div></div><p> + </p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" title="Miscellaneous Controls"><div class="titlepage"><div><div><h3 class="title"><a name="id380402"></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,93 +449,93 @@ 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" target="_top">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="id2612964"></a>Access Controls on Shares</h2></div></div></div><p> -<a class="indexterm" name="id2612972"></a> -<a class="indexterm" name="id2612978"></a> -<a class="indexterm" name="id2612986"></a> -<a class="indexterm" name="id2612993"></a> - <a class="indexterm" name="id2613000"></a> + </p></td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="sect1" title="Access Controls on Shares"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id380718"></a>Access Controls on Shares</h2></div></div></div><p> +<a class="indexterm" name="id380726"></a> +<a class="indexterm" name="id380732"></a> +<a class="indexterm" name="id380739"></a> +<a class="indexterm" name="id380746"></a> + <a class="indexterm" name="id380753"></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="id2613023"></a> -<a class="indexterm" name="id2613030"></a> -<a class="indexterm" name="id2613036"></a> +<a class="indexterm" name="id380772"></a> +<a class="indexterm" name="id380779"></a> +<a class="indexterm" name="id380786"></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="id2613053"></a> -<a class="indexterm" name="id2613060"></a> -<a class="indexterm" name="id2613067"></a> -<a class="indexterm" name="id2613073"></a> +<a class="indexterm" name="id380799"></a> +<a class="indexterm" name="id380805"></a> +<a class="indexterm" name="id380812"></a> +<a class="indexterm" name="id380819"></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> utility has been compiled and installed on your system, then you can examine the contents of this file 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="id2613112"></a>Share Permissions Management</h3></div></div></div><p> + </p><div class="sect2" title="Share Permissions Management"><div class="titlepage"><div><div><h3 class="title"><a name="id380854"></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="id2613123"></a>Windows NT4 Workstation/Server</h4></div></div></div><p> -<a class="indexterm" name="id2613131"></a> -<a class="indexterm" name="id2613138"></a> -<a class="indexterm" name="id2613145"></a> -<a class="indexterm" name="id2613152"></a> + </p><div class="sect3" title="Windows NT4 Workstation/Server"><div class="titlepage"><div><div><h4 class="title"><a name="id380864"></a>Windows NT4 Workstation/Server</h4></div></div></div><p> +<a class="indexterm" name="id380872"></a> +<a class="indexterm" name="id380878"></a> +<a class="indexterm" name="id380885"></a> +<a class="indexterm" name="id380892"></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 web site <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673" target="_top">support</a> section. - </p><div class="procedure"><a name="id2613173"></a><p class="title"><b>Procedure 16.2. Instructions</b></p><ol type="1"><li><p> + </p><div class="procedure" title="Procedure 16.2. Instructions"><a name="id380909"></a><p class="title"><b>Procedure 16.2. Instructions</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> Launch the <span class="application">NT4 Server Manager</span> and click on the Samba server you want to administer. From the menu select <span class="guimenu">Computer</span>, then click on <span class="guimenuitem">Shared Directories</span>. - </p></li><li><p> + </p></li><li class="step" title="Step 2"><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="id2613228"></a>Windows 200x/XP</h4></div></div></div><p> -<a class="indexterm" name="id2613236"></a> -<a class="indexterm" name="id2613243"></a> -<a class="indexterm" name="id2613250"></a> -<a class="indexterm" name="id2613257"></a> + </p></li></ol></div></div><div class="sect3" title="Windows 200x/XP"><div class="titlepage"><div><div><h4 class="title"><a name="id380962"></a>Windows 200x/XP</h4></div></div></div><p> +<a class="indexterm" name="id380970"></a> +<a class="indexterm" name="id380977"></a> +<a class="indexterm" name="id380984"></a> +<a class="indexterm" name="id380990"></a> On <span class="application">MS Windows NT4/200x/XP</span> systems, ACLs on the share itself are set using tools like the MS Explorer. For example, in Windows 200x, right-click on the shared folder, 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="id2613290"></a> -<a class="indexterm" name="id2613297"></a> -<a class="indexterm" name="id2613303"></a> +<a class="indexterm" name="id381021"></a> +<a class="indexterm" name="id381027"></a> +<a class="indexterm" name="id381034"></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>. - </p><div class="procedure"><a name="id2613327"></a><p class="title"><b>Procedure 16.3. Instructions</b></p><ol type="1"><li><p> + </p><div class="procedure" title="Procedure 16.3. Instructions"><a name="id381056"></a><p class="title"><b>Procedure 16.3. Instructions</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> After launching the MMC with the Computer Management snap-in, click the menu item <span class="guimenuitem">Action</span> and select <span class="guilabel">Connect to another computer</span>. If you are not logged onto a domain you will be prompted to enter a domain login user identifier and a password. This will authenticate you to the domain. If you are already logged in with administrative privilege, this step is not offered. - </p></li><li><p> + </p></li><li class="step" title="Step 2"><p> If the Samba server is not shown in the <span class="guilabel">Select Computer</span> box, type in the name of the target Samba server in the field <span class="guilabel">Name:</span>. Now click the on <span class="guibutton">[+]</span> next to <span class="guilabel">System Tools</span>, then on the <span class="guibutton">[+]</span> next to <span class="guilabel">Shared Folders</span> in the left panel. - </p></li><li><p> -<a class="indexterm" name="id2613408"></a> + </p></li><li class="step" title="Step 3"><p> +<a class="indexterm" name="id381131"></a> In the right panel, double-click on the share on which you wish to set access control permissions. Then click the tab <span class="guilabel">Share Permissions</span>. It is now possible to add access control entities to the shared folder. Remember to set what type of access (full control, change, read) you wish to assign for each entry. - </p></li></ol></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> + </p></li></ol></div><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> Be careful. If you take away all permissions from the <code class="constant">Everyone</code> user without removing this user, effectively no user will be able to access the share. This is a result of what is known as 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="id2613459"></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="id2613465"></a>Managing UNIX Permissions Using NT Security Dialogs</h3></div></div></div><p> - <a class="indexterm" name="id2613474"></a> + </p></div></div></div></div><div class="sect1" title="MS Windows Access Control Lists and UNIX Interoperability"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id381176"></a>MS Windows Access Control Lists and UNIX Interoperability</h2></div></div></div><div class="sect2" title="Managing UNIX Permissions Using NT Security Dialogs"><div class="titlepage"><div><div><h3 class="title"><a name="id381182"></a>Managing UNIX Permissions Using NT Security Dialogs</h3></div></div></div><p> + <a class="indexterm" name="id381190"></a> Windows NT clients can use their native security settings dialog box to view and modify the underlying UNIX permissions. </p><p> @@ -544,12 +544,12 @@ mystic:/home/hannibal > rm filename </p><p> Samba does not attempt to go beyond POSIX ACLs, so the various finer-grained access control options provided in Windows are actually ignored. - </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> All access to UNIX/Linux system files via Samba is controlled by the operating system file access controls. 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="id2613512"></a>Viewing File Security on a Samba Share</h3></div></div></div><p> + </p></div></div><div class="sect2" title="Viewing File Security on a Samba Share"><div class="titlepage"><div><div><h3 class="title"><a name="id381222"></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 @@ -560,7 +560,7 @@ mystic:/home/hannibal > rm filename to add auditing requirements to a file if the user is logged on as the NT administrator. This dialog is nonfunctional with a Samba share at this time, because the only useful button, the <span class="guibutton">Add</span> button, will not currently allow a list of users to be seen. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613583"></a>Viewing File Ownership</h3></div></div></div><p> + </p></div><div class="sect2" title="Viewing File Ownership"><div class="titlepage"><div><div><h3 class="title"><a name="id381286"></a>Viewing File Ownership</h3></div></div></div><p> Clicking on the <span class="guibutton">Ownership</span> button brings up a dialog box telling you who owns the given file. The owner name will be displayed like this: </p><pre class="screen"> @@ -574,7 +574,7 @@ mystic:/home/hannibal > rm filename If the parameter <a class="link" href="smb.conf.5.html#NTACLSUPPORT" target="_top">nt acl support</a> is set to <code class="constant">false</code>, the file owner will be shown as the NT user <span class="emphasis"><em>Everyone</em></span>. </p><p> -<a class="indexterm" name="id2613657"></a> +<a class="indexterm" name="id381354"></a> The <span class="guibutton">Take Ownership</span> button will not allow you to change the ownership of this file to yourself (clicking it will display a dialog box complaining that the user as whom you are currently logged onto the NT client cannot be found). The reason for this is that changing the ownership of a file is a privileged @@ -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="id2613686"></a> -<a class="indexterm" name="id2613692"></a> -<a class="indexterm" name="id2613699"></a> +<a class="indexterm" name="id381379"></a> +<a class="indexterm" name="id381385"></a> +<a class="indexterm" name="id381392"></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="id2613726"></a>Viewing File or Directory Permissions</h3></div></div></div><p> + </p></div><div class="sect2" title="Viewing File or Directory Permissions"><div class="titlepage"><div><div><h3 class="title"><a name="id381416"></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,10 +603,10 @@ 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="id2613810"></a>File Permissions</h4></div></div></div><p> + </p><div class="sect3" title="File Permissions"><div class="titlepage"><div><div><h4 class="title"><a name="id381493"></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 + <span class="quote">“<span class="quote">r</span>”</span>, <span class="quote">“<span class="quote">w</span>”</span>, and <span class="quote">“<span class="quote">x</span>”</span> bits mapped into the corresponding NT permissions. The UNIX world permissions are mapped into the global NT group <code class="constant">Everyone</code>, followed by the list of permissions allowed for the UNIX world. The UNIX owner and group permissions are displayed as an NT <span class="guiicon">user</span> icon and an NT <span class="guiicon">local group</span> icon, respectively, followed by the list @@ -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="id2613904"></a>Directory Permissions</h4></div></div></div><p> + </p></div><div class="sect3" title="Directory Permissions"><div class="titlepage"><div><div><h4 class="title"><a name="id381576"></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="id2613942"></a>Modifying File or Directory Permissions</h3></div></div></div><p> + </p></div></div><div class="sect2" title="Modifying File or Directory Permissions"><div class="titlepage"><div><div><h3 class="title"><a name="id381607"></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 @@ -653,7 +653,7 @@ mystic:/home/hannibal > rm filename permissions</em></span> entry will appear as the NT <code class="literal">O</code> flag, as described above. This allows you to add permissions back to a file or directory once you have removed them from a triplet component. </p><p> - Because UNIX supports only the “<span class="quote">r</span>”, “<span class="quote">w</span>”, and “<span class="quote">x</span>” bits of an NT ACL, if + Because UNIX supports only the <span class="quote">“<span class="quote">r</span>”</span>, <span class="quote">“<span class="quote">w</span>”</span>, and <span class="quote">“<span class="quote">x</span>”</span> bits of an NT ACL, if other NT security attributes such as <code class="constant">Delete Access</code> are selected, they will be ignored when applied on the Samba server. </p><p> @@ -665,10 +665,10 @@ 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="id2614099"></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" title="Interaction with the Standard Samba “create mask” Parameters"><div class="titlepage"><div><div><h3 class="title"><a name="id381747"></a>Interaction with the Standard Samba <span class="quote">“<span class="quote">create mask</span>”</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" target="_top">security mask</a></p></li><li><p><a class="link" href="smb.conf.5.html#FORCESECURITYMODE" target="_top">force security mode</a></p></li><li><p><a class="link" href="smb.conf.5.html#DIRECTORYSECURITYMASK" target="_top">directory security mask</a></p></li><li><p><a class="link" href="smb.conf.5.html#FORCEDIRECTORYSECURITYMODE" target="_top">force directory security mode</a></p></li></ul></div><p> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><a class="link" href="smb.conf.5.html#SECURITYMASK" target="_top">security mask</a></p></li><li class="listitem"><p><a class="link" href="smb.conf.5.html#FORCESECURITYMODE" target="_top">force security mode</a></p></li><li class="listitem"><p><a class="link" href="smb.conf.5.html#DIRECTORYSECURITYMASK" target="_top">directory security mask</a></p></li><li class="listitem"><p><a class="link" href="smb.conf.5.html#FORCEDIRECTORYSECURITYMODE" target="_top">force directory security mode</a></p></li></ul></div><p> </p><p> When a user clicks on <span class="guibutton">OK</span> to apply the @@ -719,14 +719,14 @@ 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="id2614420"></a><em class="parameter"><code>security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2614431"></a><em class="parameter"><code>force security mode = 0</code></em></td></tr><tr><td><a class="indexterm" name="id2614443"></a><em class="parameter"><code>directory security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id2614455"></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="id2614468"></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>”) + </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id382036"></a><em class="parameter"><code>security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id382047"></a><em class="parameter"><code>force security mode = 0</code></em></td></tr><tr><td><a class="indexterm" name="id382058"></a><em class="parameter"><code>directory security mask = 0777</code></em></td></tr><tr><td><a class="indexterm" name="id382070"></a><em class="parameter"><code>force directory security mode = 0</code></em></td></tr></table></div><div class="sect2" title="Interaction with the Standard Samba File Attribute Mapping"><div class="titlepage"><div><div><h3 class="title"><a name="id382083"></a>Interaction with the Standard Samba File Attribute Mapping</h3></div></div></div><div class="note" title="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">“<span class="quote">read-only</span>”</span>) into the UNIX permissions of a file. This means there can be a conflict between the permission bits set via the security dialog and the permission bits set by the file attribute mapping. </p></div><p> If a file has no UNIX read access for the owner, it will show up - as “<span class="quote">read-only</span>” in the standard file attributes tabbed dialog. + as <span class="quote">“<span class="quote">read-only</span>”</span> in the standard file attributes tabbed dialog. Unfortunately, this dialog is the same one that contains the security information in another tab. </p><p> @@ -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="id2614541"></a>Windows NT/200X ACLs and POSIX ACLs Limitations</h3></div></div></div><p> + </p></div><div class="sect2" title="Windows NT/200X ACLs and POSIX ACLs Limitations"><div class="titlepage"><div><div><h3 class="title"><a name="id382146"></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="id2614599"></a>UNIX POSIX ACL Overview</h4></div></div></div><p> + </p><div class="sect3" title="UNIX POSIX ACL Overview"><div class="titlepage"><div><div><h4 class="title"><a name="id382190"></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="id2614660"></a>Mapping of Windows File ACLs to UNIX POSIX ACLs</h4></div></div></div><p> + </p></div><div class="sect3" title="Mapping of Windows File ACLs to UNIX POSIX ACLs"><div class="titlepage"><div><div><h4 class="title"><a name="id382231"></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="id2614930"></a>Mapping of Windows Directory ACLs to UNIX POSIX ACLs</h4></div></div></div><p> + </p></div><div class="sect3" title="Mapping of Windows Directory ACLs to UNIX POSIX ACLs"><div class="titlepage"><div><div><h4 class="title"><a name="id382488"></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. @@ -824,23 +824,23 @@ default:other:--- <-- inherited permissions for everyone (other) Directory permissions function in much the same way as shown for file permissions, but there are some notable exceptions and a few peculiarities that the astute administrator will want to take into account in the setting up of directory permissions. - </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2614954"></a>Common Errors</h2></div></div></div><p> + </p></div></div></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id382508"></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="id2614965"></a>Users Cannot Write to a Public Share</h3></div></div></div><p> +</p><div class="sect2" title="Users Cannot Write to a Public Share"><div class="titlepage"><div><div><h3 class="title"><a name="id382518"></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"> + <span class="quote">“<span class="quote"> We are facing some troubles with file/directory permissions. I can log on the domain as admin user (root), and there's a public share on which everyone needs to have permission to create/modify files, but only root can change the file, no one else can. We need to constantly go to the server to <strong class="userinput"><code>chgrp -R users *</code></strong> and <strong class="userinput"><code>chown -R nobody *</code></strong> to allow other users to change the file. - </span>” + </span>”</span> </p><p> Here is one way the problem can be solved: - </p><div class="procedure"><ol type="1"><li><p> + </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> Go to the top of the directory that is shared. - </p></li><li><p> + </p></li><li class="step" title="Step 2"><p> Set the ownership to whatever public user and group you want </p><pre class="screen"> <code class="prompt">$ </code>find `directory_name' -type d -exec chown user:group {}\; @@ -848,20 +848,20 @@ are examples recently taken from the mailing list. <code class="prompt">$ </code>find `directory_name' -type f -exec chmod 0775 {}\; <code class="prompt">$ </code>find `directory_name' -type f -exec chown user:group {}\; </pre><p> - </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The above will set the <code class="constant">SGID bit</code> on all directories. Read your UNIX/Linux man page on what that does. This ensures that all files and directories that are created in the directory tree will be owned by the current user and will be owned by the group that owns the directory in which it is created. - </p></div></li><li><p> + </p></div></li><li class="step" title="Step 3"><p> Directory is <em class="replaceable"><code>/foodbar</code></em>: </p><pre class="screen"> <code class="prompt">$ </code><strong class="userinput"><code>chown jack:engr /foodbar</code></strong> </pre><p> - </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This is the same as doing:</p><pre class="screen"> + </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This is the same as doing:</p><pre class="screen"> <code class="prompt">$ </code><strong class="userinput"><code>chown jack /foodbar</code></strong> <code class="prompt">$ </code><strong class="userinput"><code>chgrp engr /foodbar</code></strong> -</pre></div></li><li><p>Now type: +</pre></div></li><li class="step" title="Step 4"><p>Now type: </p><pre class="screen"> <code class="prompt">$ </code><strong class="userinput"><code>chmod 2775 /foodbar</code></strong> @@ -871,7 +871,7 @@ are examples recently taken from the mailing list. </p><pre class="screen"> drwxrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar </pre><p> - </p></li><li><p>Now type: + </p></li><li class="step" title="Step 5"><p>Now type: </p><pre class="screen"> <code class="prompt">$ </code><strong class="userinput"><code>su - jill</code></strong> <code class="prompt">$ </code><strong class="userinput"><code>cd /foodbar</code></strong> @@ -884,16 +884,16 @@ drwxrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar </p><pre class="screen"> -rw-r--r-- 1 jill engr 0 2007-01-18 19:41 Afile </pre><p> - </p></li><li><p> + </p></li><li class="step" title="Step 6"><p> If the user that must have write permission in the directory is not a member of the group <span class="emphasis"><em>engr</em></span> set in the <code class="filename">smb.conf</code> entry for the share: - </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2615272"></a><em class="parameter"><code>force group = engr</code></em></td></tr></table><p> - </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615288"></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> + </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id382810"></a><em class="parameter"><code>force group = engr</code></em></td></tr></table><p> + </p></li></ol></div></div><div class="sect2" title="File Operations Done as root with force user Set"><div class="titlepage"><div><div><h3 class="title"><a name="id382825"></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" target="_top">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" target="_top">force user</a> has been set. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2615334"></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></div><div class="sect2" title="MS Word with Samba Changes Owner of File"><div class="titlepage"><div><div><h3 class="title"><a name="id382869"></a>MS Word with Samba Changes Owner of File</h3></div></div></div><p> + <span class="emphasis"><em>Question:</em></span> <span class="quote">“<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>”</span> </p><p> <span class="emphasis"><em>Answer:</em></span> Word does the following when you modify/change a Word document: MS Word creates a new document with a temporary name. Word then closes the old document and deletes it, then renames the new document to the original document name. @@ -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="id2615413"></a><em class="parameter"><code>force create mode = 0660</code></em></td></tr><tr><td><a class="indexterm" name="id2615424"></a><em class="parameter"><code>force directory mode = 0770</code></em></td></tr></table><p> + </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id382935"></a><em class="parameter"><code>force create mode = 0660</code></em></td></tr><tr><td><a class="indexterm" name="id382946"></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. |