summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/security/forcedirectorysecuritymode.xml
blob: 8c35ccbf8ad67418651515603540d3719f8d49e5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
<samba:parameter name="force directory security mode"
                 context="S"
                 xmlns:samba="http://samba.org/common">
<listitem>
    <para>This parameter controls what UNIX permission bits 
    can be modified when a Windows NT client is manipulating the UNIX 
    permission on a directory using the native NT security dialog box.</para>

    <para>This parameter is applied as a mask (OR'ed with) to the 
    changed permission bits, thus forcing any bits in this mask that 
    the user may have modified to be on. Essentially, one bits in this 
    mask may be treated as a set of bits that, when modifying security 
    on a directory, the user has always set to be 'on'.</para>

    <para>If not set explicitly this parameter is 000, which 
    allows a user to modify all the user/group/world permissions on a 
    directory without restrictions.</para>

    <para><emphasis>Note</emphasis> that users who can access the 
    Samba server through other means can easily bypass this restriction, 
    so it is primarily useful for standalone &quot;appliance&quot; systems.  
    Administrators of most normal systems will probably want to leave
    it set as 0000.</para>

    <para>See also the <link linkend="DIRECTORYSECURITYMASK"><parameter moreinfo="none">
    directory security mask</parameter></link>, <link linkend="SECURITYMASK">
    <parameter moreinfo="none">security mask</parameter></link>, 
    <link linkend="FORCESECURITYMODE"><parameter moreinfo="none">force security mode
    </parameter></link> parameters.</para>

    <para>Default: <command moreinfo="none">force directory security mode = 0</command></para>

    <para>Example: <command moreinfo="none">force directory security mode = 700</command></para>
</listitem>
</samba:parameter>