Ignore:
Timestamp:
Nov 14, 2012, 12:59:34 PM (13 years ago)
Author:
Silvan Scherrer
Message:

Samba Server: update vendor to 3.6.0

Location:
vendor/current/docs-xml
Files:
19 added
13 deleted
101 edited

Legend:

Unmodified
Added
Removed

  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml

    r414 r740  
    490490        <para>
    491491<indexterm><primary>extended attributes</primary></indexterm>
    492 <indexterm><primary>immutible</primary></indexterm>
     492<indexterm><primary>immutable</primary></indexterm>
    493493<indexterm><primary>chattr</primary></indexterm>
    494494<indexterm><primary>CAP_LINUX_IMMUTABLE</primary></indexterm>
    495495        The specific semantics of the extended attributes are not consistent across UNIX and UNIX-like systems such as Linux.
    496496        For example, it is possible on some implementations of the extended attributes to set a flag that prevents the directory
    497         or file from being deleted. The extended attribute that may achieve this is called the <constant>immutible</constant> bit.
    498         Unfortunately, the implementation of the immutible flag is NOT consistent with published documentation. For example, the
     497        or file from being deleted. The extended attribute that may achieve this is called the <constant>immutable</constant> bit.
     498        Unfortunately, the implementation of the immutable flag is NOT consistent with published documentation. For example, the
    499499        man page for the <command>chattr</command> on SUSE Linux 9.2 says:
    500500<screen>
    … …  
    504504CAP_LINUX_IMMUTABLE capability can set or clear this attribute.
    505505</screen>
    506         A simple test can be done to check if the immutible flag is supported on files in the file system of the Samba host
     506        A simple test can be done to check if the immutable flag is supported on files in the file system of the Samba host
    507507        server.
    508508        </para>
    … …  
    527527mystic:/home/hannibal > rm filename
    528528</screen>
    529         It will not be possible to delete the file if the immutible flag is correctly honored.
     529        It will not be possible to delete the file if the immutable flag is correctly honored.
    530530        </para></step>
    531531        </procedure>
    532532
    533533        <para>
    534         On operating systems and file system types that support the immutible bit, it is possible to create directories
     534        On operating systems and file system types that support the immutable bit, it is possible to create directories
    535535        that cannot be deleted. Check the man page on your particular host system to determine whether or not
    536536        immutable directories are writable. If they are not, then the entire directory and its contents will effectively
    … …  
    874874<indexterm><primary>Computer Management</primary></indexterm>
    875875        At this time Samba does not provide a tool for configuring access control settings on the share
    876         itself the only way to create those settings is to use either the NT4 Server Manager or the Windows 200x
     876        itself.  The only way to create those settings is to use either the NT4 Server Manager or the Windows 200x
    877877        Microsoft Management Console (MMC) for Computer Management. There are currently no plans to provide
    878878        this capability in the Samba command-line tool set.

  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Printing.xml

    r414 r740  
    523523<para>
    524524The following is a discussion of the settings from <link linkend="extbsdpr">Extended BSD Printing
    525 Configuration</link> <link linkend="extbsdpr">Extended BSD Printing Configuration</link>.
     525Configuration</link>.
    526526</para>
    527527
    … …  
    10391039in the Samba print command is <parameter>%$variable</parameter>.) To give you a working
    10401040<smbconfoption name="print command"/> example, the following will log a print job
    1041 to <filename>/tmp/print.log</filename>, print the file, then remove it. The semicolon (<quote>;</quote>
     1041to <filename>/tmp/print.log</filename>, print the file, then remove it. The semicolon (<quote>;</quote>)
    10421042is the usual separator for commands in shell scripts:
    10431043</para>
    … …  
    13191319</screen>
    13201320                 you can still mount it from any client. This can also be done from the
    1321                 <guimenu>Connect network drive menu></guimenu> from Windows Explorer.
     1321                <guimenu>Connect network drive</guimenu> menu from Windows Explorer.
    13221322                </para></listitem>
    13231323        </varlistentry>
    … …  
    16421642<indexterm><primary>UNC notation</primary></indexterm>
    16431643<indexterm><primary>Windows Explorer</primary></indexterm>
    1644 <indexterm><primary></primary></indexterm>
    16451644Since the <smbconfsection name="[print$]"/> share is usually accessible through the <guiicon>Network
    16461645Neighborhood</guiicon>, you can also use the UNC notation from Windows Explorer to poke at it. The Windows

  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-RightsAndPriviliges.xml

    r414 r740  
    370370
    371371<sect2>
    372 <title>Privileges Suppored by Windows 2000 Domain Controllers</title>
     372<title>Privileges Supported by Windows 2000 Domain Controllers</title>
    373373
    374374<para>

  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml

    r414 r740  
    9494<indexterm><primary>idmap gid</primary></indexterm>
    9595<indexterm><primary>idmap backend</primary></indexterm>
    96 <indexterm><primary>LDAP</primary></indexterm>
    9796                Winbind maintains a database called winbind_idmap.tdb in which it stores
    9897                mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only
    … …  
    211210        names as they would <quote>native</quote> UNIX names. They can chown files
    212211        so they are owned by NT domain users or even login to the
    213         UNIX machine and run a UNIX X-Window session as a domain user.</para>
     212        UNIX machine and run a UNIX X Window session as a domain user.</para>
    214213
    215214        <para>
    … …  
    572571<indexterm><primary>PAM</primary></indexterm>
    573572<indexterm><primary>back up</primary></indexterm>
    574 <indexterm><primary>boot disk`</primary></indexterm>
     573<indexterm><primary>boot disk</primary></indexterm>
    575574If you have a Samba configuration file that you are currently using, <emphasis>BACK IT UP!</emphasis>
    576575If your system already uses PAM, <emphasis>back up the <filename>/etc/pam.d</filename> directory
    … …  
    603602To allow domain users the ability to access Samba shares and files, as well as potentially other services
    604603provided by your Samba machine, PAM must be set up properly on your
    605 machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed
    606 on your system. Please refer to the PAM Web site <ulink url="http://www.kernel.org/pub/linux/libs/pam/"/>.
     604machine. In order to compile the Winbind modules, the PAM development libraries should be installed
     605on your system. Please refer to the <ulink url="http://www.kernel.org/pub/linux/libs/pam/">PAM Web Site</ulink>.
    607606</para>
    608607</sect2>
    … …  
    977976<indexterm><primary>/etc/init.d/samba</primary></indexterm>
    978977<indexterm><primary>/usr/local/samba/bin</primary></indexterm>
    979 <indexterm><primary></primary></indexterm>
    980 <indexterm><primary></primary></indexterm>
    981 <indexterm><primary></primary></indexterm>
    982978The &winbindd; daemon needs to start up after the &smbd; and &nmbd; daemons are running.  To accomplish this
    983979task, you need to modify the startup scripts of your system.  They are located at
    … …  
    11201116
    11211117<para>
    1122 Again, if you would like to run Samba in dual daemon mode, replace:
     1118Again, if you would like to run winbindd in dual daemon mode, replace:
    11231119<programlisting>
    11241120/usr/local/samba/sbin/winbindd
    … …  
    12351231<indexterm><primary>ftp access</primary></indexterm>
    12361232The <filename>/etc/pam.d/ftp</filename> file can be changed to allow Winbind ftp access in a manner similar to
    1237 the samba file. My <filename>/etc/pam.d/ftp</filename> file was changed to look like this:
     1233the <filename>/etc/pam.d/samba</filename>Samba file. My <filename>/etc/pam.d/ftp</filename> file was changed to look like this:
    12381234<programlisting>
    12391235auth       required     /lib/security/pam_listfile.so item=user sense=deny \

  • vendor/current/docs-xml/Samba3-HOWTO/manpages.xml

    r414 r740  
    1818        <xi:include href="../manpages-3/lmhosts.5.xml"/>
    1919        <xi:include href="../manpages-3/log2pcap.1.xml"/>
    20         <xi:include href="../manpages-3/mount.cifs.8.xml"/>
    2120        <xi:include href="../manpages-3/net.8.xml"/>
    2221        <xi:include href="../manpages-3/nmbd.8.xml"/>
    … …  
    4948        <xi:include href="../manpages-3/wbinfo.1.xml"/>
    5049        <xi:include href="../manpages-3/winbindd.8.xml"/>
    51         <xi:include href="../manpages-3/umount.cifs.8.xml"/>
    5250        <xi:include href="../manpages-3/vfs_audit.8.xml"/>
    5351        <xi:include href="../manpages-3/vfs_cacheprime.8.xml"/>

  • vendor/current/docs-xml/build/catalog.xml.in

    r414 r740  
    77    <rewriteURI
    88                        uriStartString="http://www.samba.org/samba/DTD/"
    9                         rewritePrefix="file://@BUILDDIR@/build/DTD/"/>
     9                        rewritePrefix="file://@abs_top_builddir@/build/DTD/"/>
    1010
    1111    <rewriteURI
    1212                        uriStartString="http://www.gnu.org/licenses/"
    13                         rewritePrefix="file://@BUILDDIR@/Samba3-ByExample/"/>
     13                        rewritePrefix="file://@abs_top_builddir@/Samba3-ByExample/"/>
    1414</catalog>

  • vendor/current/docs-xml/manpages-3/eventlogadm.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    2121
    2222                <command>eventlogadm</command>
     23                <arg><option>-s</option></arg>
    2324                <arg><option>-d</option></arg>
    2425                <arg><option>-h</option></arg>
    … …  
    3334        <cmdsynopsis>
    3435                <command>eventlogadm</command>
     36                <arg><option>-s</option></arg>
    3537                <arg><option>-d</option></arg>
    3638                <arg><option>-h</option></arg>
    … …  
    4345        <cmdsynopsis>
    4446                <command>eventlogadm</command>
     47                <arg><option>-s</option></arg>
    4548                <arg><option>-d</option></arg>
    4649                <arg><option>-h</option></arg>
    … …  
    7376
    7477        <variablelist>
     78                <varlistentry>
     79                <term>
     80                <option>-s</option>
     81                <replaceable>FILENAME</replaceable>
     82                </term>
     83                <listitem><para>
     84                The <command>-s</command> option causes <command>eventlogadm</command> to load the
     85                configuration file given as FILENAME instead of the default one used by Samba.
     86                </para></listitem>
     87                </varlistentry>
    7588
    7689                <varlistentry>

  • vendor/current/docs-xml/manpages-3/findsmb.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/idmap_ad.8.xml

    r478 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    2626        classes and relative attribute/value pairs to the user and
    2727        group objects in the AD.</para>
     28
     29        <para>
     30        Note that the idmap_ad module has changed considerably since
     31        Samba versions 3.0 and 3.2.
     32        Currently, the <parameter>ad</parameter> backend
     33        does not work as the the default idmap backend, but one has
     34        to configure it separately for each domain for which one wants
     35        to use it, using disjoint ranges. One usually needs to configure
     36        a writeable default idmap range, using for example the
     37        <parameter>tdb</parameter> or <parameter>ldap</parameter>
     38        backend, in order to be able to map the BUILTIN sids and
     39        possibly other trusted domains. The writeable default config
     40        is also needed in order to be able to create group mappings.
     41        This catch-all default idmap configuration should have a range
     42        that is disjoint from any explicitly configured domain with
     43        idmap backend <parameter>ad</parameter>. See the example below.
     44        </para>
    2845</refsynopsisdiv>
    2946
    … …  
    6986        <programlisting>
    7087        [global]
    71         idmap backend = tdb
    72         idmap uid = 1000000-1999999
    73         idmap gid = 1000000-1999999
     88        idmap config * : backend = tdb
     89        idmap config * : range = 1000000-1999999
    7490
    7591        idmap config CORP : backend  = ad

  • vendor/current/docs-xml/manpages-3/idmap_adex.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    6767        <programlisting>
    6868        [global]
    69         idmap backend = adex
    70         idmap uid = 1000-4000000000
    71         idmap gid = 1000-4000000000
     69        idmap config * : backend = adex
     70        idmap config * : range = 1000-4000000000
    7271
    7372        winbind nss info = adex

  • vendor/current/docs-xml/manpages-3/idmap_hash.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    5353        <programlisting>
    5454        [global]
    55         idmap backend = hash
    56         idmap uid = 1000-4000000000
    57         idmap gid = 1000-4000000000
     55        idmap config * : backend = hash
     56        idmap config * : range = 1000-4000000000
    5857
    5958        winbind nss info = hash

  • vendor/current/docs-xml/manpages-3/idmap_ldap.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    2828        In contrast to read only backends like idmap_rid, it is an allocating
    2929        backend: This means that it needs to allocate new user and group IDs in
    30         order to create new mappings. The allocator can be provided by the
    31         idmap_ldap backend itself or by any other allocating backend like
    32         idmap_tdb or idmap_tdb2. This is configured with the
    33         parameter <parameter>idmap alloc backend</parameter>.
     30        order to create new mappings.
    3431        </para>
    3532
    36         <para>
    37         Note that in order for this (or any other allocating) backend to
    38         function at all, the default backend needs to be writeable.
    39         The ranges used for uid and gid allocation are the default ranges
    40         configured by &quot;idmap uid&quot; and &quot;idmap gid&quot;.
    41         </para>
    42 
    43         <para>
    44         Furthermore, since there is only one global allocating backend
    45         responsible for all domains using writeable idmap backends,
    46         any explicitly configured domain with idmap backend ldap
    47         should have the same range as the default range, since it needs
    48         to use the global uid / gid allocator. See the example below.
    49         </para>
    5033</refsynopsisdiv>
    5134
    … …  
    5740                <term>ldap_base_dn = DN</term>
    5841                <listitem><para>
    59                         Defines the directory base suffix to use when searching for
     42                        Defines the directory base suffix to use for
    6043                        SID/uid/gid mapping entries.  If not defined, idmap_ldap will default
    6144                        to using the &quot;ldap idmap suffix&quot; option from smb.conf.
    … …  
    6649                <term>ldap_user_dn = DN</term>
    6750                <listitem><para>
    68                         Defines the user DN to be used for authentication. If absent an
    69                         anonymous bind will be performed.
     51                        Defines the user DN to be used for authentication.
     52                        The secret for authenticating this user should be
     53                        stored with net idmap secret
     54                        (see <citerefentry><refentrytitle>net</refentrytitle>
     55                        <manvolnum>8</manvolnum></citerefentry>).
     56                        If absent, the ldap credentials from the ldap passdb configuration
     57                        are used, and if these are also absent, an anonymous
     58                        bind will be performed as last fallback.
    7059                </para></listitem>
    7160                </varlistentry>
    … …  
    7463                <term>ldap_url = ldap://server/</term>
    7564                <listitem><para>
    76                         Specifies the LDAP server to use when searching for existing
     65                        Specifies the LDAP server to use for
    7766                        SID/uid/gid map entries. If not defined, idmap_ldap will
    7867                        assume that ldap://localhost/ should be used.
    … …  
    8574                        Defines the available matching uid and gid range for which the
    8675                        backend is authoritative.
    87                         If the parameter is absent, Winbind fails over to use the
    88                         &quot;idmap uid&quot; and &quot;idmap gid&quot; options
    89                         from smb.conf.
    9076                </para></listitem>
    9177                </varlistentry>
    92         </variablelist>
    93 </refsect1>
    94 
    95 <refsect1>
    96         <title>IDMAP ALLOC OPTIONS</title>
    97 
    98         <variablelist>
    99                 <varlistentry>
    100                 <term>ldap_base_dn = DN</term>
    101                 <listitem><para>
    102                         Defines the directory base suffix under which new SID/uid/gid mapping
    103                         entries should be stored.  If not defined, idmap_ldap will default
    104                         to using the &quot;ldap idmap suffix&quot; option from smb.conf.
    105                 </para></listitem>
    106                 </varlistentry>
    107 
    108                 <varlistentry>
    109                 <term>ldap_user_dn = DN</term>
    110                 <listitem><para>
    111                         Defines the user DN to be used for authentication. If absent an
    112                         anonymous bind will be performed.
    113                 </para></listitem>
    114                 </varlistentry>
    115 
    116                 <varlistentry>
    117                 <term>ldap_url = ldap://server/</term>
    118                 <listitem><para>
    119                         Specifies the LDAP server to which modify/add/delete requests should
    120                         be sent.  If not defined, idmap_ldap will assume that ldap://localhost/
    121                         should be used.
    122                 </para></listitem>
    123                 </varlistentry>
    12478        </variablelist>
    12579</refsect1>
    … …  
    12983
    13084        <para>
    131         The follow sets of a LDAP configuration which uses two LDAP
    132         directories, one for storing the ID mappings and one for retrieving
    133         new IDs.
     85        The following example shows how an ldap directory is used as the
     86        default idmap backend. It also configures the idmap range and base
     87        directory suffix. The secret for the ldap_user_dn has to be set with
     88        &quot;net idmap secret '*' password&quot;.
    13489        </para>
    13590
    13691        <programlisting>
    13792        [global]
    138         idmap backend = ldap:ldap://localhost/
    139         idmap uid = 1000000-1999999
    140         idmap gid = 1000000-1999999
     93        idmap config * : backend      = ldap
     94        idmap config * : range        = 1000000-1999999
     95        idmap config * : ldap_url     = ldap://localhost/
     96        idmap config * : ldap_base_dn = ou=idmap,dc=example,dc=com
     97        idmap config * : ldap_user_dn = cn=idmap_admin,dc=example,dc=com
     98        </programlisting>
    14199
    142         idmap alloc backend = ldap
    143         idmap alloc config : ldap_url   = ldap://id-master/
    144         idmap alloc config : ldap_base_dn = ou=idmap,dc=example,dc=com
     100        <para>
     101        This example shows how ldap can be used as a readonly backend while
     102        tdb is the default backend used to store the mappings.
     103        It adds an explicit configuration for some domain DOM1, that
     104        uses the ldap idmap backend. Note that a range disjoint from the
     105        default range is used.
     106        </para>
     107
     108        <programlisting>
     109        [global]
     110        # "backend = tdb" is redundant here since it is the default
     111        idmap config * : backend = tdb
     112        idmap config * : range = 1000000-1999999
     113
     114        idmap config DOM1 : backend = ldap
     115        idmap config DOM1 : range = 2000000-2999999
     116        idmap config DOM1 : read only = yes
     117        idmap config DOM1 : ldap_url = ldap://server/
     118        idmap config DOM1 : ldap_base_dn = ou=idmap,dc=dom1,dc=example,dc=com
     119        idmap config DOM1 : ldap_user_dn = cn=idmap_admin,dc=dom1,dc=example,dc=com
    145120        </programlisting>
    146121</refsect1>

  • vendor/current/docs-xml/manpages-3/idmap_nss.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    3939        <programlisting>
    4040        [global]
    41         idmap backend = tdb
    42         idmap uid = 1000000-1999999
    43         idmap gid = 1000000-1999999
     41        idmap config * : backend = tdb
     42        idmap config * : range = 1000000-1999999
    4443
    4544        idmap config SAMBA : backend  = nss

  • vendor/current/docs-xml/manpages-3/idmap_rid.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    2222        mapping scheme to map UIDs/GIDs and SIDs. No database is required
    2323        in this case as the mapping is deterministic.</para>
     24
     25        <para>
     26        Note that the idmap_rid module has changed considerably since Samba
     27        versions 3.0. and 3.2.
     28        Currently, there should to be an explicit idmap configuration for each
     29        domain that should use the idmap_rid backend, using disjoint ranges.
     30        One usually needs to define a writeable default idmap range, using
     31        a backent like <parameter>tdb</parameter> or <parameter>ldap</parameter>
     32        that can create unix ids, in order to be able to map the BUILTIN sids
     33        and other domains, and also in order to be able to create group mappings.
     34        See the example below.
     35        </para>
     36
     37        <para>
     38        Note that the old syntax
     39        <parameter>idmap backend = rid:"DOM1=range DOM2=range2 ..."</parameter>
     40        is not supported any more since Samba version 3.0.25.
     41        </para>
    2442</refsynopsisdiv>
    2543
    … …  
    89107        workgroup = MAIN
    90108
    91         idmap backend = tdb
    92         idmap uid = 1000000-1999999
    93         idmap gid = 1000000-1999999
     109        idmap config * : backend        = tdb
     110        idmap config * : range          = 1000000-1999999
    94111
    95112        idmap config MAIN : backend     = rid

  • vendor/current/docs-xml/manpages-3/idmap_tdb.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    2828        In contrast to read only backends like idmap_rid, it is an allocating
    2929        backend: This means that it needs to allocate new user and group IDs in
    30         order to create new mappings. The allocator can be provided by the
    31         idmap_tdb backend itself or by any other allocating backend like
    32         idmap_ldap or idmap_tdb2. This is configured with the
    33         parameter <parameter>idmap alloc backend</parameter>.
    34         </para>
    35 
    36         <para>
    37         Note that in order for this (or any other allocating) backend to
    38         function at all, the default backend needs to be writeable.
    39         The ranges used for uid and gid allocation are the default ranges
    40         configured by &quot;idmap uid&quot; and &quot;idmap gid&quot;.
    41         </para>
    42 
    43         <para>
    44         Furthermore, since there is only one global allocating backend
    45         responsible for all domains using writeable idmap backends,
    46         any explicitly configured domain with idmap backend tdb
    47         should have the same range as the default range, since it needs
    48         to use the global uid / gid allocator. See the example below.
     30        order to create new mappings.
    4931        </para>
    5032</refsynopsisdiv>
    … …  
    5941                        Defines the available matching uid and gid range for which the
    6042                        backend is authoritative.
    61                         If the parameter is absent, Winbind fails over to use
    62                         the &quot;idmap uid&quot; and &quot;idmap gid&quot; options
    63                         from smb.conf.
    6443                </para></listitem>
    6544                </varlistentry>
    … …  
    7251        <para>
    7352        This example shows how tdb is used as a the default idmap backend.
    74         It configures the idmap range through the global options for all
    75         domains encountered. This same range is used for uid/gid allocation.
     53        This configured range is used for uid and gid allocation.
    7654        </para>
    7755
    7856        <programlisting>
    7957        [global]
    80         # "idmap backend = tdb" is redundant here since it is the default
    81         idmap backend = tdb
    82         idmap uid = 1000000-2000000
    83         idmap gid = 1000000-2000000
    84         </programlisting>
    85 
    86         <para>
    87         This (rather theoretical) example shows how tdb can be used as the
    88         allocating backend while ldap is the default backend used to store
    89         the mappings.
    90         It adds an explicit configuration for some domain DOM1, that
    91         uses the tdb idmap backend. Note that the same range as the
    92         default uid/gid range is used, since the allocator has to serve
    93         both the default backend and the explicitly configured domain DOM1.
    94         </para>
    95 
    96         <programlisting>
    97         [global]
    98         idmap backend = ldap
    99         idmap uid = 1000000-2000000
    100         idmap gid = 1000000-2000000
    101         # use a different uid/gid allocator:
    102         idmap alloc backend = tdb
    103 
    104         idmap config DOM1 : backend = tdb
    105         idmap config DOM1 : range = 1000000-2000000
     58        # "backend = tdb" is redundant here since it is the default
     59        idmap config * : backend = tdb
     60        idmap config * : range = 1000000-2000000
    10661        </programlisting>
    10762</refsect1>

  • vendor/current/docs-xml/manpages-3/idmap_tdb2.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    2929        In contrast to read only backends like idmap_rid, it is an allocating
    3030        backend: This means that it needs to allocate new user and group IDs in
    31         order to create new mappings. The allocator can be provided by the
    32         idmap_tdb2 backend itself or by any other allocating backend like
    33         idmap_tdb or idmap_ldap. This is configured with the
    34         parameter <parameter>idmap alloc backend</parameter>.
    35         </para>
    36 
    37         <para>
    38         Note that in order for this (or any other allocating) backend to
    39         function at all, the default backend needs to be writeable.
    40         The ranges used for uid and gid allocation are the default ranges
    41         configured by &quot;idmap uid&quot; and &quot;idmap gid&quot;.
    42         </para>
    43 
    44         <para>
    45         Furthermore, since there is only one global allocating backend
    46         responsible for all domains using writeable idmap backends,
    47         any explicitly configured domain with idmap backend tdb2
    48         should have the same range as the default range, since it needs
    49         to use the global uid / gid allocator. See the example below.
     31        order to create new mappings.
    5032        </para>
    5133</refsynopsisdiv>
    … …  
    6042                        Defines the available matching uid and gid range for which the
    6143                        backend is authoritative.
    62                         If the parameter is absent, Winbind fails over to use
    63                         the &quot;idmap uid&quot; and &quot;idmap gid&quot; options
    64                         from smb.conf.
     44                </para></listitem>
     45                </varlistentry>
     46
     47                <varlistentry>
     48                <term>script</term>
     49                <listitem><para>
     50                        This option can be used to configure an external program
     51                        for performing id mappings instead of using the tdb
     52                        counter. The mappings are then stored int tdb2 idmap
     53                        database. For details see the section on IDMAP SCRIPT below.
    6554                </para></listitem>
    6655                </varlistentry>
    … …  
    7261
    7362        <para>
    74         The tdb2 idmap backend supports a script for performing id mappings
    75         through the smb.conf option <parameter>idmap : script</parameter>.
     63        The tdb2 idmap backend supports an external program for performing id mappings
     64        through the smb.conf option <parameter>idmap config * : script</parameter> or
     65        its deprecated legacy form <parameter>idmap : script</parameter>.
     66        </para>
     67
     68        <para>
     69        The mappings obtained by the script are then stored in the idmap tdb2
     70        database instead of mappings created by the incrementing id counters.
     71        It is therefore important that the script covers the complete range of
     72        SIDs that can be passed in for SID to Unix ID mapping, since otherwise
     73        SIDs unmapped by the script might get mapped to IDs that had
     74        previously been mapped by the script.
     75        </para>
     76
     77        <para>
    7678        The script should accept the following command line options.
    7779        </para>
    … …  
    9496        ERR:yyyy
    9597        </programlisting>
    96 
    97         <para>
    98         Note that the script should cover the complete range of SIDs
    99         that can be passed in for SID to Unix ID mapping, since otherwise
    100         SIDs unmapped by the script might get mapped to IDs that had
    101         previously been mapped by the script.
    102         </para>
    10398</refsect1>
    10499
    … …  
    108103        <para>
    109104        This example shows how tdb2 is used as a the default idmap backend.
    110         It configures the idmap range through the global options for all
    111         domains encountered. This same range is used for uid/gid allocation.
    112105        </para>
    113106
    114107        <programlisting>
    115108        [global]
    116         idmap backend = tdb2
    117         idmap uid = 1000000-2000000
    118         idmap gid = 1000000-2000000
     109        idmap config * : backend = tdb2
     110        idmap config * : range = 1000000-2000000
     111        </programlisting>
     112
     113        <para>
     114        This example shows how tdb2 is used as a the default idmap backend
     115        using an external program via the script parameter:
     116        </para>
     117
     118        <programlisting>
     119        [global]
     120        idmap config * : backend = tdb2
     121        idmap config * : range = 1000000-2000000
     122        idmap config * : script = /usr/local/samba/bin/idmap_script.sh
    119123        </programlisting>
    120124</refsect1>

  • vendor/current/docs-xml/manpages-3/libsmbclient.7.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">7</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/lmhosts.5.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">File Formats and Conventions</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/log2pcap.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/net.8.xml

    r478 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    796796
    797797</refsect3>
    798 
     798<refsect3>
     799<title>RPC TRUSTDOM LIST</title>
     800
     801<para>List all interdomain trust relationships.</para>
     802
     803</refsect3>
     804</refsect2>
     805
     806<refsect2>
     807<title>RPC TRUST</title>
     808
     809<refsect3>
     810<title>RPC TRUST CREATE</title>
     811
     812<para>Create a trust trust object by calling lsaCreateTrustedDomainEx2.
     813The can be done on a single server or on two servers at once with the
     814possibility to use a random trust password.</para>
     815
     816<variablelist><title>Options:</title>
     817<varlistentry>
     818<term>otherserver</term>
     819<listitem><para>Domain controller of the second domain</para></listitem>
     820</varlistentry>
     821
     822<varlistentry>
     823<term>otheruser</term>
     824<listitem><para>Admin user in the second domain</para></listitem>
     825</varlistentry>
     826
     827<varlistentry>
     828<term>otherdomainsid</term>
     829<listitem><para>SID of the second domain</para></listitem>
     830</varlistentry>
     831
     832<varlistentry>
     833<term>other_netbios_domain</term>
     834<listitem><para>NetBIOS (short) name of the second domain</para></listitem>
     835</varlistentry>
     836
     837<varlistentry>
     838<term>otherdomain</term>
     839<listitem><para>DNS (full) name of the second domain</para></listitem>
     840</varlistentry>
     841
     842<varlistentry>
     843<term>trustpw</term>
     844<listitem><para>Trust password</para></listitem>
     845</varlistentry>
     846</variablelist>
     847
     848<variablelist><title>Examples:</title>
     849<varlistentry>
     850<term>Create a trust object on srv1.dom1.dom for the domain dom2</term>
     851<listitem><literallayout>
     852net rpc trust create \
     853    otherdomainsid=S-x-x-xx-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxx \
     854    other_netbios_domain=dom2 \
     855    otherdomain=dom2.dom \
     856    trustpw=12345678 \
     857    -S srv1.dom1.dom
     858</literallayout></listitem>
     859</varlistentry>
     860<varlistentry>
     861<term>Create a trust relationship between dom1 and dom2</term>
     862<listitem><literallayout>
     863net rpc trust create \
     864    otherserver=srv2.dom2.test \
     865    otheruser=dom2adm \
     866    -S srv1.dom1.dom
     867</literallayout></listitem>
     868</varlistentry>
     869</variablelist>
     870</refsect3>
     871
     872<refsect3>
     873<title>RPC TRUST DELETE</title>
     874
     875<para>Delete a trust trust object by calling lsaDeleteTrustedDomain.
     876The can be done on a single server or on two servers at once.</para>
     877
     878<variablelist><title>Options:</title>
     879<varlistentry>
     880<term>otherserver</term>
     881<listitem><para>Domain controller of the second domain</para></listitem>
     882</varlistentry>
     883
     884<varlistentry>
     885<term>otheruser</term>
     886<listitem><para>Admin user in the second domain</para></listitem>
     887</varlistentry>
     888
     889<varlistentry>
     890<term>otherdomainsid</term>
     891<listitem><para>SID of the second domain</para></listitem>
     892</varlistentry>
     893</variablelist>
     894
     895<variablelist><title>Examples:</title>
     896<varlistentry>
     897<term>Delete a trust object on srv1.dom1.dom for the domain dom2</term>
     898<listitem><literallayout>
     899net rpc trust delete \
     900    otherdomainsid=S-x-x-xx-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxx \
     901    -S srv1.dom1.dom
     902</literallayout></listitem>
     903</varlistentry>
     904<varlistentry>
     905<term>Delete a trust relationship between dom1 and dom2</term>
     906<listitem><literallayout>
     907net rpc trust delete \
     908    otherserver=srv2.dom2.test \
     909    otheruser=dom2adm \
     910    -S srv1.dom1.dom
     911</literallayout></listitem>
     912</varlistentry>
     913</variablelist>
     914</refsect3>
     915
     916</refsect2>
     917
     918<refsect2>
    799919<refsect3>
    800920<title>RPC RIGHTS</title>
    … …  
    12681388
    12691389<refsect2>
    1270 <title>IDMAP SECRET &lt;DOMAIN&gt;|ALLOC &lt;secret&gt;</title>
     1390<title>IDMAP SECRET &lt;DOMAIN&gt; &lt;secret&gt;</title>
    12711391
    12721392<para>
    … …  
    12771397
    12781398</refsect2>
     1399
     1400<refsect2>
     1401
     1402<title>IDMAP DELETE [-f] [--db=&lt;DB&gt;] &lt;ID&gt;</title>
     1403
     1404<para>
     1405Delete a mapping sid &lt;-&gt; gid or sid &lt;-&gt; uid from the IDMAP database.
     1406The mapping is given by &lt;ID&gt; which may either be a sid: S-x-..., a gid: "GID number" or a uid: "UID number".
     1407Use -f to delete an invalid partial mapping &lt;ID&gt; -&gt; xx
     1408</para>
     1409<para>
     1410  Use "smbcontrol all idmap ..." to notify running smbd instances.
     1411  See the <citerefentry><refentrytitle>smbcontrol</refentrytitle>
     1412  <manvolnum>1</manvolnum></citerefentry> manpage for details.
     1413</para>
     1414</refsect2>
     1415
     1416<refsect2>
     1417
     1418<title>IDMAP CHECK [-v] [-r] [-a] [-T] [-f] [-l] [--db=&lt;DB&gt;]</title>
     1419
     1420<para>
     1421  Check and repair the IDMAP database. If no option is given a read only check
     1422  of the database is done. Among others an interactive or automatic repair mode
     1423  may be chosen with one of the following options:
     1424
     1425  <variablelist>
     1426    <varlistentry><term>-r|--repair</term>
     1427    <listitem><para>
     1428      Interactive repair mode, ask a lot of questions.
     1429    </para></listitem>
     1430    </varlistentry>
     1431
     1432    <varlistentry><term>-a|--auto</term>
     1433    <listitem><para>
     1434      Noninteractive repair mode, use default answers.
     1435    </para></listitem>
     1436    </varlistentry>
     1437
     1438    <varlistentry><term>-v|--verbose</term>
     1439      <listitem><para>
     1440        Produce more output.
     1441      </para></listitem>
     1442    </varlistentry>
     1443
     1444    <varlistentry><term>-f|--force</term>
     1445      <listitem><para>
     1446        Try to apply changes, even if they do not apply cleanly.
     1447      </para></listitem>
     1448    </varlistentry>
     1449
     1450    <varlistentry><term>-T|--test</term>
     1451      <listitem><para>
     1452        Dry run, show what changes would be made but don't touch anything.
     1453      </para></listitem>
     1454    </varlistentry>
     1455
     1456    <varlistentry><term>-l|--lock</term>
     1457      <listitem><para>
     1458        Lock the database while doing the check.
     1459      </para></listitem>
     1460    </varlistentry>
     1461
     1462    <varlistentry><term>--db &lt;DB&gt;</term>
     1463      <listitem><para>
     1464        Check the specified database.
     1465      </para></listitem>
     1466    </varlistentry>
     1467    <varlistentry><term></term>
     1468      <listitem><para>
     1469      </para></listitem>
     1470    </varlistentry>
     1471  </variablelist>
     1472
     1473  It reports about the finding of the following errors:
     1474
     1475  <variablelist>
     1476    <varlistentry><term>Missing reverse mapping:</term>
     1477    <listitem><para>
     1478      A record with mapping A-&gt;B where there is no B-&gt;A. Default action
     1479      in repair mode is to "fix" this by adding the reverse mapping.
     1480    </para></listitem>
     1481    </varlistentry>
     1482
     1483    <varlistentry><term>Invalid mapping:</term>
     1484    <listitem><para>
     1485      A record with mapping A-&gt;B where B-&gt;C. Default action
     1486      is to "delete" this record.
     1487    </para></listitem>
     1488  </varlistentry>
     1489
     1490  <varlistentry><term>Missing or invalid HWM:</term>
     1491    <listitem><para>
     1492      A high water mark is not at least equal to the largest ID in the
     1493      database. Default action is to "fix" this by setting it to the
     1494      largest ID found +1.
     1495    </para></listitem>
     1496  </varlistentry>
     1497
     1498  <varlistentry><term>Invalid record:</term>
     1499    <listitem><para>
     1500      Something we failed to parse. Default action is to "edit" it
     1501      in interactive and "delete" it in automatic mode.
     1502    </para></listitem>
     1503  </varlistentry>
     1504</variablelist>
     1505</para>
     1506</refsect2>
     1507
    12791508
    12801509<refsect2>
    … …  
    16181847
    16191848<refsect2>
     1849<title>REGISTRY</title>
     1850<para>
     1851Manipulate Samba's registry.
     1852</para>
     1853
     1854<para>The registry commands are:
     1855<simplelist>
     1856<member>net registry enumerate   - Enumerate registry keys and values.</member>
     1857<member>net registry enumerate_recursive - Enumerate registry key and its subkeys.</member>
     1858<member>net registry createkey   - Create a new registry key.</member>
     1859<member>net registry deletekey   - Delete a registry key.</member>
     1860<member>net registry deletekey_recursive - Delete a registry key with subkeys.</member>
     1861<member>net registry getvalue    - Print a registry value.</member>
     1862<member>net registry getvalueraw - Print a registry value (raw format).</member>
     1863<member>net registry setvalue    - Set a new registry value.</member>
     1864<member>net registry increment   - Increment a DWORD registry value under a lock.
     1865</member>
     1866<member>net registry deletevalue - Delete a registry value.</member>
     1867<member>net registry getsd       - Get security descriptor.</member>
     1868<member>net registry getsd_sdd1  - Get security descriptor in sddl format.
     1869</member>
     1870<member>net registry setsd_sdd1  - Set security descriptor from sddl format
     1871string.</member>
     1872<member>net registry import      - Import a registration entries (.reg) file.
     1873</member>
     1874<member>net registry export      - Export a registration entries (.reg) file.
     1875</member>
     1876<member>net registry convert     - Convert a registration entries (.reg) file.
     1877</member>
     1878</simplelist>
     1879</para>
     1880
     1881<refsect3>
     1882  <title>REGISTRY ENUMERATE <replaceable>key</replaceable> </title>
     1883  <para>Enumerate subkeys and values of <emphasis>key</emphasis>.
     1884  </para>
     1885</refsect3>
     1886
     1887<refsect3>
     1888  <title>REGISTRY ENUMERATE_RECURSIVE <replaceable>key</replaceable> </title>
     1889  <para>Enumerate values of <emphasis>key</emphasis> and its subkeys.
     1890  </para>
     1891</refsect3>
     1892
     1893<refsect3>
     1894  <title>REGISTRY CREATEKEY <replaceable>key</replaceable> </title>
     1895  <para>Create a new <emphasis>key</emphasis> if not yet existing.
     1896  </para>
     1897</refsect3>
     1898
     1899<refsect3>
     1900  <title>REGISTRY DELETEKEY <replaceable>key</replaceable> </title>
     1901  <para>Delete the given <emphasis>key</emphasis> and its
     1902  values from the registry, if it has no subkeys.
     1903  </para>
     1904</refsect3>
     1905
     1906<refsect3>
     1907  <title>REGISTRY DELETEKEY_RECURSIVE <replaceable>key</replaceable> </title>
     1908  <para>Delete the given <emphasis>key</emphasis> and all of its
     1909  subkeys and values from the registry.
     1910  </para>
     1911</refsect3>
     1912
     1913<refsect3>
     1914  <title>REGISTRY GETVALUE <replaceable>key</replaceable> <!--
     1915  --><replaceable>name</replaceable></title>
     1916
     1917  <para>Output type and actual value of the value <emphasis>name</emphasis>
     1918  of the given <emphasis>key</emphasis>.
     1919  </para>
     1920</refsect3>
     1921
     1922<refsect3>
     1923  <title>REGISTRY GETVALUERAW <replaceable>key</replaceable> <!--
     1924  --><replaceable>name</replaceable></title>
     1925  <para>Output the actual value of the value <emphasis>name</emphasis>
     1926  of the given <emphasis>key</emphasis>.
     1927  </para>
     1928</refsect3>
     1929
     1930<refsect3>
     1931  <title>REGISTRY SETVALUE <replaceable>key</replaceable> <!--
     1932  --><replaceable>name</replaceable> <replaceable>type</replaceable> <!--
     1933  --><replaceable>value</replaceable> ...<!--
     1934  --></title>
     1935
     1936  <para>Set the value <emphasis>name</emphasis>
     1937  of an existing <emphasis>key</emphasis>.
     1938  <emphasis>type</emphasis> may be one of
     1939  <emphasis>sz</emphasis>, <emphasis>multi_sz</emphasis> or
     1940  <emphasis>dword</emphasis>.
     1941  In case of <emphasis>multi_sz</emphasis> <replaceable>value</replaceable> may
     1942  be given multiple times.
     1943  </para>
     1944</refsect3>
     1945
     1946<refsect3>
     1947  <title>REGISTRY INCREMENT <replaceable>key</replaceable> <!--
     1948  --><replaceable>name</replaceable> <replaceable>[inc]</replaceable><!--
     1949  --></title>
     1950
     1951  <para>Increment the DWORD value <emphasis>name</emphasis>
     1952  of <emphasis>key</emphasis> by <replaceable>inc</replaceable>
     1953  while holding a g_lock.
     1954  <emphasis>inc</emphasis> defaults to 1.
     1955  </para>
     1956</refsect3>
     1957
     1958<refsect3>
     1959  <title>REGISTRY DELETEVALUE <replaceable>key</replaceable> <!--
     1960  --><replaceable>name</replaceable></title>
     1961
     1962  <para>Delete the value <emphasis>name</emphasis>
     1963  of the given <emphasis>key</emphasis>.
     1964  </para>
     1965</refsect3>
     1966
     1967<refsect3>
     1968  <title>REGISTRY GETSD <replaceable>key</replaceable></title>
     1969
     1970  <para>Get the security descriptor of the given <emphasis>key</emphasis>.
     1971  </para>
     1972</refsect3>
     1973
     1974<refsect3>
     1975  <title>REGISTRY GETSD_SDDL <replaceable>key</replaceable></title>
     1976
     1977  <para>Get the security descriptor of the given <emphasis>key</emphasis> as a
     1978  Security Descriptor Definition Language (SDDL) string.
     1979  </para>
     1980</refsect3>
     1981
     1982<refsect3>
     1983  <title>REGISTRY SETSD_SDDL <replaceable>key</replaceable><!--
     1984  --><replaceable>sd</replaceable></title>
     1985
     1986  <para>Set the security descriptor of the given <emphasis>key</emphasis> from a
     1987  Security Descriptor Definition Language (SDDL) string <emphasis>sd</emphasis>.
     1988  </para>
     1989</refsect3>
     1990
     1991<refsect3>
     1992  <title>REGISTRY IMPORT <replaceable>file</replaceable><!--
     1993  --><replaceable>[opt]</replaceable></title>
     1994
     1995  <para>Import a registration entries (.reg) <emphasis>file</emphasis>.
     1996  </para>
     1997</refsect3>
     1998
     1999<refsect3>
     2000  <title>REGISTRY EXPORT <replaceable>key</replaceable><!--
     2001  --><replaceable>file</replaceable><!--
     2002  --><replaceable>[opt]</replaceable></title>
     2003
     2004  <para>Export a <emphasis>key</emphasis> to a registration entries (.reg)
     2005  <emphasis>file</emphasis>.
     2006  </para>
     2007</refsect3>
     2008
     2009<refsect3>
     2010  <title>REGISTRY CONVERT <replaceable>in</replaceable> <!--
     2011  --><replaceable>out</replaceable> <!--
     2012  --><replaceable>[[inopt] outopt]</replaceable></title>
     2013
     2014  <para>Convert a registration entries (.reg) file <emphasis>in</emphasis>.
     2015  </para>
     2016</refsect3>
     2017
     2018
     2019</refsect2>
     2020
     2021<refsect2>
    16202022<title>EVENTLOG</title>
    16212023

  • vendor/current/docs-xml/manpages-3/nmbd.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/nmblookup.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/ntlm_auth.1.xml

    r478 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    157157                user). </para>
    158158
    159                 <para>Curently implemented parameters from the
     159                <para>Currently implemented parameters from the
    160160                external program to the helper are:</para>
    161161                <variablelist>

  • vendor/current/docs-xml/manpages-3/pam_winbind.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">8</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/pdbedit.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/profiles.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/rpcclient.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    6363
    6464                <varlistentry>
    65                 <term>-c|--command='command string'</term>
    66                 <listitem><para>execute semicolon separated commands (listed
    67                 below)) </para></listitem>
     65                <term>-c|--command=&lt;command string&gt;</term>
     66                <listitem><para>Execute semicolon separated commands (listed
     67                below) </para></listitem>
    6868                </varlistentry>
    6969
    … …  
    268268
    269269
    270                 <varlistentry><term>deldriver</term><listitem><para>Delete the
     270                <varlistentry><term>deldriver &lt;driver&gt;</term><listitem><para>Delete the
    271271                specified printer driver for all architectures.  This
    272272                does not delete the actual driver files from the server,

  • vendor/current/docs-xml/manpages-3/samba.7.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">Miscellanea</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/sharesec.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/smb.conf.5.xml

    r414 r740  
    77        <refmiscinfo class="source">Samba</refmiscinfo>
    88        <refmiscinfo class="manual">File Formats and Conventions</refmiscinfo>
    9         <refmiscinfo class="version">3.5</refmiscinfo>
     9        <refmiscinfo class="version">3.6</refmiscinfo>
    1010</refmeta>
    1111
    … …  
    489489                    machine.  It currently recognizes Samba (<constant>Samba</constant>),
    490490                    the Linux CIFS file system (<constant>CIFSFS</constant>), OS/2, (<constant>OS2</constant>),
    491                     Windows for Workgroups (<constant>WfWg</constant>), Windows 9x/ME
     491                    Mac OS X (<constant>OSX</constant>), Windows for Workgroups (<constant>WfWg</constant>), Windows 9x/ME
    492492                    (<constant>Win95</constant>), Windows NT (<constant>WinNT</constant>),
    493493                    Windows 2000 (<constant>Win2K</constant>),
    … …  
    504504                <term>%I</term>
    505505                <listitem><para>the IP address of the client machine.</para>
     506                <para>Before 3.6.0 it could contain IPv4 mapped IPv6 addresses,
     507                        now it only contains IPv4 or IPv6 addresses.</para>
    506508                </listitem>
    507509                </varlistentry>
    … …  
    510512                <term>%i</term>
    511513                <listitem><para>the local IP address to which a client connected.</para>
     514                <para>Before 3.6.0 it could contain IPv4 mapped IPv6 addresses,
     515                        now it only contains IPv4 or IPv6 addresses.</para>
    512516                </listitem>
    513517                </varlistentry>
    … …  
    629633                <listitem><para>
    630634                controls what the default case is for new filenames (ie. files that don't currently exist in the filesystem).
    631                 Default <emphasis>lower</emphasis>.  IMPORTANT NOTE: This option will be used to modify the case of
    632                 <emphasis>all</emphasis> incoming client filenames, not just new filenames if the options <smbconfoption
    633                 name="case sensitive">yes</smbconfoption>, <smbconfoption name="preserve case">No</smbconfoption>,
    634                 <smbconfoption name="short preserve case">No</smbconfoption> are set.  This change is needed as part of the
    635                 optimisations for directories containing large numbers of files.
     635                Default <emphasis>lower</emphasis>.  IMPORTANT NOTE: As part of the optimizations for directories containing
     636                large numbers of files, the following special case applies. If the options
     637                <smbconfoption  name="case sensitive">yes</smbconfoption>, <smbconfoption name="preserve case">No</smbconfoption>, and
     638                <smbconfoption name="short preserve case">No</smbconfoption> are set, then the case of <emphasis>all</emphasis>
     639                incoming client filenames, not just new filenames, will be modified. See additional notes below.
    636640                </para></listitem>
    637641                </varlistentry>

  • vendor/current/docs-xml/manpages-3/smbcacls.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    2222                <arg choice="req">//server/share</arg>
    2323                <arg choice="req">filename</arg>
    24                 <arg choice="opt">-D acls</arg>
    25                 <arg choice="opt">-M acls</arg>
    26                 <arg choice="opt">-a acls</arg>
    27                 <arg choice="opt">-S acls</arg>
    28                 <arg choice="opt">-C name</arg>
    29                 <arg choice="opt">-G name</arg>
     24                <arg choice="opt">-D|--delete acls</arg>
     25                <arg choice="opt">-M|--modify acls</arg>
     26                <arg choice="opt">-a|--add acls</arg>
     27                <arg choice="opt">-S|--set acls</arg>
     28                <arg choice="opt">-C|--chown name</arg>
     29                <arg choice="opt">-G|--chgrp name</arg>
     30                <arg choice="opt">-I allow|romove|copy</arg>
    3031                <arg choice="opt">--numeric</arg>
    3132                <arg choice="opt">-t</arg>
    … …  
    118119               
    119120               
     121                <varlistentry>
     122                <term>-I|--inherit allow|remove|copy</term>
     123                <listitem><para>Set or unset the windows "Allow inheritable
     124                permissions" check box using the <parameter>-I</parameter>
     125                option.  To set the check box pass allow. To unset the check
     126                box pass either remove or copy. Remove will remove all
     127                inherited acls. Copy will copy all the inherited acls.
     128                </para></listitem>
     129
     130                </varlistentry>
     131
     132
     133
    120134                <varlistentry>
    121135                <term>--numeric</term>

  • vendor/current/docs-xml/manpages-3/smbclient.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    262262
    263263                <varlistentry>
    264                 <term>-P</term>
     264                <term>-P|--machine-pass</term>
    265265                <listitem><para>
    266266                Make queries to the external server using the machine account of the local server.
    … …  
    318318               
    319319                <varlistentry>
    320                 <term>-e</term>
     320                <term>-e|--encrypt</term>
    321321                <listitem><para>This command line parameter requires the remote
    322322                server support the UNIX extensions. Request that the connection be
    … …  
    470470               
    471471                <varlistentry>
    472                 <term>-c|--comand command string</term>
     472                <term>-c|--command command string</term>
    473473                <listitem><para>command string is a semicolon-separated list of
    474474                commands to be executed instead of prompting from stdin. <parameter>

  • vendor/current/docs-xml/manpages-3/smbcontrol.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    273273        </varlistentry>
    274274
     275        <varlistentry>
     276        <term>idmap</term>
     277        <listitem><para>Notify about changes of id mapping. Can be sent
     278        to <constant>smbd</constant> or (not implemented yet) <constant>winbindd</constant>.
     279        </para></listitem>
     280
     281        <variablelist>
     282          <varlistentry>
     283            <term>flush [uid|gid]</term>
     284            <listitem><para>Flush caches for sid &lt;-&gt; gid and/or sid &lt;-&gt; uid mapping.
     285            </para></listitem>
     286          </varlistentry>
     287          <varlistentry>
     288            <term>delete &lt;ID&gt;</term>
     289            <listitem><para>Remove a mapping from cache. The mapping is given by &lt;ID&gt;
     290            which may either be a sid: S-x-..., a gid: "GID number" or a uid: "UID number".
     291            </para></listitem>
     292          </varlistentry>
     293          <varlistentry>
     294            <term>kill &lt;ID&gt;</term>
     295            <listitem><para>Remove a mapping from cache. Terminate <constant>smbd</constant> if
     296            the id is currently in use.</para></listitem>
     297          </varlistentry>
     298        </variablelist>
     299        </varlistentry>
     300
    275301</variablelist>
    276302</refsect1>

  • vendor/current/docs-xml/manpages-3/smbcquotas.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/smbd.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/smbget.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    124124        <varlistentry>
    125125                <term>-f, --rcfile</term>
    126                 <listitem><para>Use specified rcfile. This will be loaded in the order it was specified - e.g. if you specify any options before this one, they might get overriden by the contents of the rcfile.</para></listitem>
     126                <listitem><para>Use specified rcfile. This will be loaded in the order it was specified - e.g. if you specify any options before this one, they might get overridden by the contents of the rcfile.</para></listitem>
    127127        </varlistentry>
    128128

  • vendor/current/docs-xml/manpages-3/smbgetrc.5.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">File Formats and Conventions</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/smbpasswd.5.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">File Formats and Conventions</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/smbpasswd.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/smbspool.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/smbstatus.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/smbtar.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/smbtree.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/swat.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/tdbbackup.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/tdbdump.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/tdbtool.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/testparm.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    2424                <arg choice="opt">-h</arg>
    2525                <arg choice="opt">-v</arg>
    26                 <arg choice="opt">-L &lt;servername&gt;</arg>
    2726                <arg choice="opt">-t &lt;encoding&gt;</arg>
    2827                <arg choice="req">config filename</arg>
    … …  
    7473                &stdarg.version;
    7574               
    76                 <varlistentry>
    77                 <term>-L servername</term>
    78                 <listitem><para>Sets the value of the %L macro to <replaceable>servername</replaceable>.
    79                 This is useful for testing include files specified with the
    80                 %L macro. </para></listitem>
    81                 </varlistentry>
    82 
    8375                <varlistentry>
    8476                <term>-v</term>

  • vendor/current/docs-xml/manpages-3/vfs_acl_tdb.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_acl_xattr.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_audit.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_cacheprime.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_cap.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_catia.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_commit.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_default_quota.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_dirsort.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_extd_audit.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_fake_perms.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_fileid.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_full_audit.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    185185                <para>LIST is a list of VFS operations that should be
    186186                recorded if they succeed. Operations are specified using
    187                 the names listed above.
     187                the names listed above. Operations can be unset by prefixing
     188                the names with "!".
    188189                </para>
    189190
    … …  
    196197                <para>LIST is a list of VFS operations that should be
    197198                recorded if they failed. Operations are specified using
    198                 the names listed above.
     199                the names listed above. Operations can be unset by prefixing
     200                the names with "!".
    199201                </para>
    200202
    … …  
    233235        <para>Log file and directory open operations on the [records]
    234236        share using the LOCAL7 facility and ALERT priority, including
    235         the username and IP address:</para>
     237        the username and IP address. Logging excludes the open VFS function
     238        on failures:</para>
    236239
    237240<programlisting>
    … …  
    241244        <smbconfoption name="full_audit:prefix">%u|%I</smbconfoption>
    242245        <smbconfoption name="full_audit:success">open opendir</smbconfoption>
    243         <smbconfoption name="full_audit:failure">all</smbconfoption>
     246        <smbconfoption name="full_audit:failure">all !open</smbconfoption>
    244247        <smbconfoption name="full_audit:facility">LOCAL7</smbconfoption>
    245248        <smbconfoption name="full_audit:priority">ALERT</smbconfoption>

  • vendor/current/docs-xml/manpages-3/vfs_gpfs.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    6161                <varlistentry>
    6262
     63                <term>gpfs:sharemodes = [ yes | no ]</term>
     64                <listitem>
     65                <para>
     66                Enable/Disable cross node sharemode handling for GPFS.
     67                </para>
     68
     69                <itemizedlist>
     70                <listitem><para>
     71                <command>yes(default)</command> - propagate sharemodes across all GPFS nodes.
     72                </para></listitem>
     73                <listitem><para>
     74                <command>no</command> - do not propagate sharemodes across all GPFS nodes.
     75                This should only be used if the GPFS file system is
     76                exclusively exported by Samba. Access by local unix application or
     77                NFS exports could lead to corrupted files.
     78                </para></listitem>
     79                </itemizedlist>
     80                </listitem>
     81
     82                </varlistentry>
     83                <varlistentry>
     84
     85                <term>gpfs:leases = [ yes | no ]</term>
     86                <listitem>
     87                <para>
     88                Enable/Disable cross node leases (oplocks) for GPFS.
     89                You should also set the <command>oplocks</command> and <command>kernel oplocks</command>
     90                options to the same value.
     91                </para>
     92
     93                <itemizedlist>
     94                <listitem><para>
     95                <command>yes(default)</command> - propagate leases across all GPFS nodes.
     96                </para></listitem>
     97                <listitem><para>
     98                <command>no</command> - do not propagate leases across all GPFS nodes.
     99                This should only be used if the GPFS file system is
     100                exclusively exported by Samba. Access by local unix application or
     101                NFS exports could lead to corrupted files.
     102                </para></listitem>
     103                </itemizedlist>
     104                </listitem>
     105
     106                </varlistentry>
     107
     108                <varlistentry>
     109
     110                <term>gpfs:hsm = [ yes | no ]</term>
     111                <listitem>
     112                <para>
     113                Enable/Disable announcing if this FS has HSM enabled.
     114                </para>
     115
     116                <itemizedlist>
     117                <listitem><para>
     118                <command>no(default)</command> - Do not announce HSM.
     119                </para></listitem>
     120                <listitem><para>
     121                <command>no</command> - Announce HSM.
     122                </para></listitem>
     123                </itemizedlist>
     124                </listitem>
     125
     126                </varlistentry>
     127
     128                <varlistentry>
     129
     130                <term>gpfs:getrealfilename = [ yes | no ]</term>
     131                <listitem>
     132                <para>
     133                Enable/Disable usage of the <command>gpfs_get_realfilename_path()</command> function.
     134                This improves the casesensitive wildcard file name access.
     135                </para>
     136
     137                <itemizedlist>
     138                <listitem><para>
     139                <command>yes(default)</command> - use <command>gpfs_get_realfilename_path()</command>.
     140                </para></listitem>
     141                <listitem><para>
     142                <command>no</command> - do not use <command>gpfs_get_realfilename_path()</command>.
     143                It seems that <command>gpfs_get_realfilename_path()</command> doesn't work on AIX.
     144                </para></listitem>
     145                </itemizedlist>
     146                </listitem>
     147
     148                </varlistentry>
     149                <varlistentry>
     150
     151                <term>gpfs:winattr = [ yes | no ]</term>
     152                <listitem>
     153                <para>
     154                Enable/Disable usage of the windows attributes in GPFS.
     155                GPFS is able to store windows file attributes e.g. HIDDEN,
     156                READONLY, SYSTEM and others natively. That means Samba doesn't
     157                need to map them to permission bits or extended attributes.
     158                </para>
     159
     160                <itemizedlist>
     161                <listitem><para>
     162                <command>no(default)</command> - do not use GPFS windows attributes.
     163                </para></listitem>
     164                <listitem><para>
     165                <command>yes</command> - use GPFS windows attributes.
     166                </para></listitem>
     167                </itemizedlist>
     168                </listitem>
     169
     170                </varlistentry>
     171                <varlistentry>
     172
     173                <term>gpfs:merge_writeappend = [ yes | no ]</term>
     174                <listitem>
     175                <para>
     176                GPFS ACLs doesn't know about the 'APPEND' right.
     177                This optionen lets Samba map the 'APPEND' right to 'WRITE'.
     178                </para>
     179
     180                <itemizedlist>
     181                <listitem><para>
     182                <command>yes(default)</command> - map 'APPEND' to 'WRITE'.
     183                </para></listitem>
     184                <listitem><para>
     185                <command>no</command> - do not map 'APPEND' to 'WRITE'.
     186                </para></listitem>
     187                </itemizedlist>
     188                </listitem>
     189
     190                </varlistentry>
     191                <varlistentry>
     192
     193                <term>gpfs:refuse_dacl_protected = [ yes | no ]</term>
     194                <listitem>
     195                <para>
     196                As GPFS does not support the ACE4_FLAG_NO_PROPAGATE NFSv4 flag (which would be
     197                the mapping for the DESC_DACL_PROTECTED flag), the status of this flag is
     198                currently silently ignored by Samba. That means that if you deselect the "Allow
     199                inheritable permissions..." checkbox in Windows' ACL dialog and then apply the
     200                ACL, the flag will be back immediately.
     201                </para>
     202                <para>
     203                To make sure that automatic migration with e.g. robocopy does not lead to
     204                ACLs silently (and unintentionally) changed, you can set
     205                <command>gpfs:refuse_dacl_protected = yes</command> to enable an explicit
     206                check for this flag and if set, it will return NT_STATUS_NOT_SUPPORTED so
     207                errors are shown up on the Windows side and the Administrator is aware of
     208                the ACLs not being settable like intended
     209                </para>
     210
     211                <itemizedlist>
     212                <listitem><para>
     213                <command>no(default)</command> - ignore the DESC_DACL_PROTECTED flags.
     214                </para></listitem>
     215                <listitem><para>
     216                <command>yes</command> - reject ACLs with DESC_DACL_PROTECTED.
     217                </para></listitem>
     218                </itemizedlist>
     219                </listitem>
     220
     221                </varlistentry>
     222                <varlistentry>
     223
    63224                <term>nfs4:mode = [ simple | special ]</term>
    64225                <listitem>
    … …  
    112273                <listitem><para><command>yes</command> - Enable chown if as supported by the under filesystem</para></listitem>
    113274                <listitem><para><command>no (default)</command> - Disable chown</para></listitem>
     275                </itemizedlist>
     276                </listitem>
     277                </varlistentry>
     278
     279                <varlistentry>
     280                <term>gpfs:syncio = [yes|no]</term>
     281                <listitem>
     282                <para>This parameter makes Samba open all files with O_SYNC.
     283                  This triggers optimizations in GPFS for workloads that
     284                  heavily share files.</para>
     285
     286                <para>Following is the behaviour of Samba for different
     287                  values:
     288                </para>
     289                <itemizedlist>
     290                <listitem><para><command>yes</command>Open files with O_SYNC
     291                </para></listitem>
     292                <listitem><para><command>no (default)</command>Open files as
     293                    normal Samba would do
     294                </para></listitem>
    114295                </itemizedlist>
    115296                </listitem>
    … …  
    135316<refsect1>
    136317        <title>CAVEATS</title>
    137         <para>The gpfs gpl libraries are required by <command>gpfs</command> VFS
    138         module during both compilation and runtime.
    139         Also this VFS module is tested to work on SLES 9/10 and RHEL 4.4
     318        <para>
     319        Depending on the version of gpfs, the <command>libgpfs_gpl</command>
     320        library or the <command>libgpfs</command> library is needed at
     321        runtime by the <command>gpfs</command> VFS module:
     322        Starting with gpfs 3.2.1 PTF8, the complete <command>libgpfs</command>
     323        is available as open source and <command>libgpfs_gpl</command> does no
     324        longer exist. With earlier versions of gpfs, only the
     325        <command>libgpfs_gpl</command> library was open source and could be
     326        used at run time.
     327        </para>
     328        <para>
     329        At build time, only the header file <command>gpfs_gpl.h</command>
     330        is required , which is a symlink to <command>gpfs.h</command> in
     331        gpfs versions newer than 3.2.1 PTF8.
    140332        </para>
    141333</refsect1>

  • vendor/current/docs-xml/manpages-3/vfs_netatalk.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_notify_fam.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_prealloc.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_preopen.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_readahead.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_readonly.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_recycle.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_scannedonly.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    226226        <title>VERSION</title>
    227227
    228         <para>This man page is correct for version 3.5.0 of the Samba suite.
     228        <para>This man page is correct for version 3.6.0 of the Samba suite.
    229229        </para>
    230230</refsect1>

  • vendor/current/docs-xml/manpages-3/vfs_shadow_copy.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_shadow_copy2.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    108108
    109109                <varlistentry>
     110                <term>shadow:sort = asc/desc, or not specified for unsorted (default)
     111                </term>
     112                <listitem>
     113                <para>By this parameter one can specify that the shadow
     114                copy directories should be sorted before they are sent to the
     115                client.  This can be beneficial as unix filesystems are usually
     116                not listed alphabetically sorted. If enabled, you typically
     117                want to specify descending order.
     118                </para>
     119                </listitem>
     120                </varlistentry>
     121
     122                <varlistentry>
     123                <term>shadow:localtime = yes/no
     124                </term>
     125                <listitem>
     126                <para>This is an optional parameter that indicates whether the
     127                snapshot names are in UTC/GMT or in local time. By default
     128                UTC is expected.
     129                </para>
     130                </listitem>
     131                </varlistentry>
     132
     133                <varlistentry>
     134                <term>shadow:format = format specification for snapshot names
     135                </term>
     136                <listitem>
     137                <para>This is an optional parameter that specifies the format
     138                specification for the naming of snapshots.  The format must
     139                be compatible with the conversion specifications recognized
     140                by str[fp]time.  The default value is "@GMT-%Y.%m.%d-%H.%M.%S".
     141                </para>
     142                </listitem>
     143                </varlistentry>
     144
     145                <varlistentry>
    110146                <term>shadow:fixinodes = yes/no
    111147                </term>
    … …  
    134170        <smbconfoption name="shadow:snapdir">/data/snaphots</smbconfoption>
    135171        <smbconfoption name="shadow:basedir">/data/home</smbconfoption>
     172        <smbconfoption name="shadow:sort">desc</smbconfoption>
    136173</programlisting>
    137174

  • vendor/current/docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    3232
    3333        <para>The <command>vfs_smb_traffic_analyzer</command> VFS module logs
    34         client write and read operations on a Samba server and sends this data
    35         over a socket to a helper program, which feeds a SQL database. More
     34        client file operations on a Samba server and sends this data
     35        over a socket to a helper program (in the following the "Receiver"),
     36        which feeds a SQL database. More
    3637        information on the helper programs can be obtained from the
    3738        homepage of the project at:
    3839        http://holger123.wordpress.com/smb-traffic-analyzer/
    39         </para>
    40         <para><command>vfs_smb_traffic_analyzer</command> currently is aware
    41         of the following VFS operations:</para>
     40        Since the VFS module depends on a receiver that is doing something with
     41        the data, it is evolving in it's development. Therefore, the module
     42        works with different protocol versions, and the receiver has to be able
     43        to decode the protocol that is used. The protocol version 1 was
     44        introduced to Samba at September 25, 2008. It was a very simple
     45        protocol, supporting only a small list of VFS operations, and had
     46        several drawbacks. The protocol version 2 is a try to solve the
     47        problems version 1 had while at the same time adding new features.
     48        With the release of Samba 3.6.0, the module will run protocol version 2
     49        by default.
     50        </para>
     51</refsect1>
     52
     53<refsect1>
     54        <title>Protocol version 1 documentation</title>
     55        <para><command>vfs_smb_traffic_analyzer</command> protocol version 1 is aware
     56                of the following VFS operations:</para>
    4257
    4358        <simplelist>
    … …  
    6580        <listitem><para><command>FILENAME</command> - the name of the file that was used by the VFS operation</para></listitem>
    6681        <listitem><para><command>TIMESTAMP</command> - a timestamp, formatted as "yyyy-mm-dd hh-mm-ss.ms" indicating when the VFS operation occured</para></listitem>
     82        <listitem><para><command>IP</command> - The IP Address (v4 or v6) of the client machine that initiated the VFS operation.</para></listitem>
    6783        </itemizedlist>
    6884
    … …  
    7389</refsect1>
    7490
    75 
    76 <refsect1>
    77         <title>OPTIONS</title>
     91<refsect1>
     92        <title>Drawbacks of protocol version 1</title>
     93        <para>Several drawbacks have been seen with protocol version 1 over time.</para>
     94        <itemizedlist>
     95        <listitem>
     96                <para>
     97                        <command>Problematic parsing - </command>
     98                        Protocol version 1 uses hyphen and comma to seperate blocks of data. Once there is a
     99                        filename with a hyphen, you will run into problems because the receiver decodes the
     100                        data in a wrong way.
     101                </para>
     102        </listitem>
     103        <listitem>
     104                <para>
     105                        <command>Insecure network transfer - </command>
     106                        Protocol version 1 sends all it's data as plaintext over the network.
     107                </para>
     108        </listitem>
     109        <listitem>
     110                <para>
     111                        <command>Limited set of supported VFS operations - </command>
     112                        Protocol version 1 supports only four VFS operations.
     113                </para>
     114        </listitem>
     115        <listitem>
     116                <para>
     117                        <command>No subreleases of the protocol - </command>
     118                        Protocol version 1 is fixed on it's version, making it unable to introduce new
     119                        features or bugfixes through compatible sub-releases.
     120                </para>
     121        </listitem>
     122        </itemizedlist>
     123</refsect1>
     124<refsect1>
     125        <title>Version 2 of the protocol</title>
     126        <para>Protocol version 2 is an approach to solve the problems introduced with protcol v1.
     127        From the users perspective, the following changes are most prominent among other enhancements:
     128        </para>
     129        <itemizedlist>
     130                <listitem>
     131                <para>
     132                The data from the module may be send encrypted, with a key stored in secrets.tdb. The
     133                Receiver then has to use the same key. The module does AES block encryption over the
     134                data to send.
     135                </para>
     136                </listitem>
     137                <listitem>
     138                <para>
     139                The module now can identify itself against the receiver with a sub-release number, where
     140                the receiver may run with a different sub-release number than the module. However, as
     141                long as both run on the V2.x protocol, the receiver will not crash, even if the module
     142                uses features only implemented in the newer subrelease. If the module uses
     143                a new feature from a newer subrelease, and the receiver runs an older protocol, it is just
     144                ignoring the functionality. Of course it is best to have both the receiver and the module
     145                running the same subrelease of the protocol.
     146                </para>
     147                </listitem>
     148                <listitem>
     149                <para>
     150                The parsing problems of protocol V1 can no longer happen, because V2 is marshalling the
     151                data packages in a proper way.
     152                </para>
     153                </listitem>
     154                <listitem>
     155                <para>
     156                The module now potientially has the ability to create data on every VFS function. As of
     157                protocol V2.0, there is support for 8 VFS functions, namely write,read,pread,pwrite,
     158                rename,chdir,mkdir and rmdir. Supporting more VFS functions is one of the targets for the
     159                upcoming sub-releases.
     160                </para>
     161                </listitem>
     162        </itemizedlist>
     163        <para>
     164                To enable protocol V2, the protocol_version vfs option has to be used (see OPTIONS).
     165        </para>
     166               
     167</refsect1>             
     168
     169<refsect1>
     170        <title>OPTIONS with protocol V1 and V2.x</title>
    78171
    79172        <variablelist>
    … …  
    112205                <listitem>
    113206                <para>The module will replace the user names with a prefix
    114                 given by STRING and a simple hash number.
     207                given by STRING and a simple hash number. In version 2.x
     208                of the protocol, the users SID will also be anonymized.
    115209                </para>
    116210
    … …  
    126220                an additional hash number. This means that any transfer data
    127221                will be mapped to a single user, leading to a total
    128                 anonymization of user related data.</para>
     222                anonymization of user related data. In version 2.x of the
     223                protocol, the users SID will also be anonymized.</para>
     224                </listitem>
     225                </varlistentry>
     226
     227                <varlistentry>
     228                <term>smb_traffic_analyzer:protocol_version = STRING</term>
     229                <listitem>
     230                <para>If STRING matches to V1, the module will use version 1 of the
     231                protocol. If STRING is not given, the module will use version 2 of the
     232                protocol, which is the default.
     233                </para>
    129234                </listitem>
    130235                </varlistentry>
    … …  
    135240<refsect1>
    136241        <title>EXAMPLES</title>
     242        <para>Running protocol V2 on share "example_share", using an internet socket.</para>
     243        <programlisting>
     244        <smbconfsection name="[example_share]"/>
     245        <smbconfoption name="path">/data/example</smbconfoption>
     246        <smbconfoption name="vfs_objects">smb_traffic_analyzer</smbconfoption>
     247        <smbconfoption name="smb_traffic_analyzer:host">examplehost</smbconfoption>
     248        <smbconfoption name="smb_traffic_analyzer:port">3491</smbconfoption>
     249        </programlisting>
    137250
    138251        <para>The module running on share "example_share", using a unix domain socket</para>
    … …  
    184297        helper tools were created by Holger Hetterich.</para>
    185298</refsect1>
    186 
    187299</refentry>

  • vendor/current/docs-xml/manpages-3/vfs_streams_depot.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_streams_xattr.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfs_xattr_tdb.8.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/vfstest.1.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/wbinfo.1.xml

    r597 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">User Commands</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    5151                <arg choice="opt">-r user</arg>
    5252                <arg choide="opt">-R|--lookup-rids</arg>
    53                 <arg choice="opt">--remove-uid-mapping uid,sid</arg>
    54                 <arg choice="opt">--remove-gid-mapping gid,sid</arg>
    5553                <arg choice="opt">-s sid</arg>
    5654                <arg choice="opt">--separator</arg>
    57                 <arg choice="opt">--sequence</arg>
    5855                <arg choice="opt">--set-auth-user user%password</arg>
    59                 <arg choice="opt">--set-uid-mapping uid,sid</arg>
    60                 <arg choice="opt">--set-gid-mapping gid,sid</arg>
    6156                <arg choice="opt">-S sid</arg>
    6257                <arg choide="opt">--sid-aliases</arg>
    … …  
    152147                the current domain to which <citerefentry><refentrytitle>winbindd</refentrytitle>
    153148                <manvolnum>8</manvolnum></citerefentry> belongs.  Currently only the
    154                 <option>--sequence</option>,
    155149                <option>-u</option>, and <option>-g</option> options honor this parameter.
    156150                </para></listitem>
    … …  
    312306
    313307                <varlistentry>
     308                <term>-P|--ping-dc</term>
     309                <listitem><para>Issue a no-effect command to our DC. This
     310                    checks if our secure channel connection to our domain
     311                    controller is still alive. It has much less impact than
     312                    wbinfo -t.
     313                </para></listitem>
     314                </varlistentry>
     315
     316                <varlistentry>
    314317                <term>-r|--user-groups <replaceable>username</replaceable></term>
    315318                <listitem><para>Try to obtain the list of UNIX group ids
    … …  
    338341                <term>--separator</term>
    339342                <listitem><para>Get the active winbind separator.
    340                 </para></listitem>
    341 
    342                 </varlistentry>
    343                 <varlistentry>
    344                 <term>--sequence</term>
    345                 <listitem><para>Show sequence numbers of all known domains.
    346343                </para></listitem>
    347344                </varlistentry>
    … …  
    427424                <listitem><para>Try to convert a UNIX user id to a Windows NT
    428425                SID.  If the uid specified does not refer to one within
    429                 the idmap uid range then the operation will fail. </para></listitem>
     426                the idmap range then the operation will fail. </para></listitem>
    430427                </varlistentry>
    431428
    … …  
    445442                </varlistentry>
    446443
    447                 <varlistentry>
    448                 <term>--remove-uid-mapping uid,sid</term>
    449                 <listitem><para>Remove an existing uid to sid mapping
    450                 entry from the IDmap backend.</para></listitem>
    451                 </varlistentry>
    452 
    453                 <varlistentry>
    454                 <term>--remove-gid-mapping gid,sid</term>
    455                 <listitem><para>Remove an existing gid to sid
    456                 mapping entry from the IDmap backend.</para></listitem>
    457                 </varlistentry>
    458 
    459                 <varlistentry>
    460                 <term>--set-uid-mapping uid,sid</term>
    461                 <listitem><para>Create a new or modify an existing uid to sid
    462                 mapping in the IDmap backend.</para></listitem>
    463                 </varlistentry>
    464 
    465                 <varlistentry>
    466                 <term>--set-gid-mapping gid,sid</term>
    467                 <listitem><para>Create a new or modify an existing gid to sid
    468                 mapping in the IDmap backend.</para></listitem>
    469                 </varlistentry>
    470 
    471444                &stdarg.version;
    472445                &stdarg.help;

  • vendor/current/docs-xml/manpages-3/winbind_krb5_locator.7.xml

    r414 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">7</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212

  • vendor/current/docs-xml/manpages-3/winbindd.8.xml

    r478 r740  
    88        <refmiscinfo class="source">Samba</refmiscinfo>
    99        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
    10         <refmiscinfo class="version">3.5</refmiscinfo>
     10        <refmiscinfo class="version">3.6</refmiscinfo>
    1111</refmeta>
    1212
    … …  
    4646        service to <command>smbd</command>, <command>ntlm_auth</command>
    4747        and the <command>pam_winbind.so</command> PAM module, by managing connections to
    48         domain controllers.  In this configuraiton the
    49         <smbconfoption name="idmap uid"/> and
    50         <smbconfoption name="idmap gid"/>
    51         parameters are not required. (This is known as `netlogon proxy only mode'.)</para>
     48        domain controllers.  In this configuration the
     49        <smbconfoption name="idmap config * : range"/>
     50        parameter is not required. (This is known as `netlogon proxy only mode'.)</para>
    5251
    5352        <para> The Name Service Switch allows user
    … …  
    247246                <smbconfoption name="winbind separator"/></para></listitem>
    248247                <listitem><para>
    249                 <smbconfoption name="idmap uid"/></para></listitem>
    250                 <listitem><para>
    251                 <smbconfoption name="idmap gid"/></para></listitem>
    252                 <listitem><para>
    253                 <smbconfoption name="idmap backend"/></para></listitem>
     248                <smbconfoption name="idmap config * : range"/></para></listitem>
     249                <listitem><para>
     250                <smbconfoption name="idmap config * : backend"/></para></listitem>
    254251                <listitem><para>
    255252                <smbconfoption name="winbind cache time"/></para></listitem>
    … …  
    341338        template shell = /bin/bash
    342339        template homedir = /home/%D/%U
    343         idmap uid = 10000-20000
    344         idmap gid = 10000-20000
     340        idmap config * : range = 10000-20000
    345341        workgroup = DOMAIN
    346342        security = domain
    … …  
    375371        then in general the user and groups ids allocated by winbindd will not
    376372        be the same.  The user and group ids will only be valid for the local
    377         machine, unless a shared <smbconfoption name="idmap backend"/> is configured.</para>
     373        machine, unless a shared <smbconfoption name="idmap config * : backend"/> is configured.</para>
    378374
    379375        <para>If the the Windows NT SID to UNIX user and group id mapping

  • vendor/current/docs-xml/smbdotconf/locking/posixlocking.xml

    r414 r740  
    99        to map this internal database to POSIX locks. This means that file locks obtained by SMB clients are
    1010        consistent with those seen by POSIX compliant applications accessing the files via a non-SMB
    11         method (e.g. NFS or local file access). You should never need to disable this parameter.
     11        method (e.g. NFS or local file access). It is very unlikely that you need to set this parameter
     12        to "no", unless you are sharing from an NFS mount, which is not a good idea in the first place.
    1213        </para>
    1314</description>

  • vendor/current/docs-xml/smbdotconf/logon/enableprivileges.xml

    r414 r740  
    66<description>
    77        <para>
    8         This parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either
     8        This deprecated parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either
    99         <command>net rpc rights</command> or one of the Windows user and group manager tools.  This parameter is
    1010        enabled by default. It can be disabled to prevent members of the Domain Admins group from being able to

  • vendor/current/docs-xml/smbdotconf/misc/timeoffset.xml

    r414 r740  
    55                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
    66<description>
    7         <para>This parameter is a setting in minutes to add
     7        <para>This deprecated parameter is a setting in minutes to add
    88        to the normal GMT to local time conversion. This is useful if
    99        you are serving a lot of PCs that have incorrect daylight
    1010        saving time handling.</para>
     11
     12        <note><para>This option is deprecated, and will be removed in the next major release</para></note>
    1113</description>
    1214

  • vendor/current/docs-xml/smbdotconf/printing/addportcommand.xml

    r414 r740  
    1616    </itemizedlist>
    1717               
    18     <para>The deviceURI is in the for of socket://&lt;hostname&gt;[:&lt;portnumber&gt;]
     18    <para>The deviceURI is in the format of socket://&lt;hostname&gt;[:&lt;portnumber&gt;]
    1919        or lpd://&lt;hostname&gt;/&lt;queuename&gt;.</para>
    2020</description>

  • vendor/current/docs-xml/smbdotconf/printing/printcapcachetime.xml

    r414 r740  
    66<description>
    77    <para>This option specifies the number of seconds before the printing
    8     subsystem is again asked for the known printers.  If the value
    9     is greater than 60 the initial waiting time is set to 60 seconds
    10     to allow an earlier first rescan of the printing subsystem.
     8    subsystem is again asked for the known printers.
    119    </para>
    1210

  • vendor/current/docs-xml/smbdotconf/protocol/usespnego.xml

    r414 r740  
    55                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
    66<description>
    7     <para>This variable controls controls whether samba will try
     7    <para>This deprecated variable controls controls whether samba will try
    88    to use Simple and Protected NEGOciation (as specified by rfc2478) with
    99    WindowsXP and Windows2000 clients to agree upon an authentication mechanism.

  • vendor/current/docs-xml/smbdotconf/security/clientntlmv2auth.xml

    r414 r740  
    1111
    1212    <para>If enabled, only an NTLMv2 and LMv2 response (both much more
    13     secure than earlier versions) will be sent.  Many servers
     13    secure than earlier versions) will be sent.  Older servers
    1414    (including NT4 &lt; SP4, Win9x and Samba 2.2) are not compatible with
    15     NTLMv2.  </para>
     15    NTLMv2 when not in an NTLMv2 supporting domain</para>
    1616
    1717    <para>Similarly, if enabled, NTLMv1, <command
    … …  
    2525    moreinfo="none">client lanman auth</command>.  </para>
    2626
    27     <para>Note that some sites (particularly
    28     those following 'best practice' security polices) only allow NTLMv2
    29         responses, and not the weaker LM or NTLM.</para>
     27    <para>Note that Windows Vista and later versions already use
     28    NTLMv2 by default, and some sites (particularly those following
     29    'best practice' security polices) only allow NTLMv2 responses, and
     30    not the weaker LM or NTLM.</para>
    3031</description>
    31 <value type="default">no</value>
     32<value type="default">yes</value>
    3233</samba:parameter>

  • vendor/current/docs-xml/smbdotconf/security/guestok.xml

    r414 r740  
    1010    Privileges will be those of the <smbconfoption name="guest account"/>.</para>
    1111
    12     <para>This paramater nullifies the benifits of setting
     12    <para>This parameter nullifies the benefits of setting
    1313    <smbconfoption name="restrict anonymous">2</smbconfoption>
    1414        </para>

  • vendor/current/docs-xml/smbdotconf/security/passwordlevel.xml

    r414 r740  
    1414    negotiation request/response.</para>
    1515
    16     <para>This parameter defines the maximum number of characters
     16    <para>This deprecated parameter defines the maximum number of characters
    1717    that may be upper case in passwords.</para>
    1818

  • vendor/current/docs-xml/smbdotconf/security/passwordserver.xml

    r414 r740  
    1111    to do all its username/password validation using a specific remote server.</para>
    1212
    13     <para>This option sets the name or IP address of the password server to use.
    14     New syntax has been added to support defining the port to use when connecting
    15     to the server the case of an ADS realm.  To define a port other than the
    16     default LDAP port of 389, add the port number using a colon after the
    17     name or IP address (e.g. 192.168.1.100:389).  If you do not specify a port,
    18     Samba will use the standard LDAP port of tcp/389.  Note that port numbers
    19     have no effect on password servers for Windows NT 4.0 domains or netbios
    20     connections.</para>
     13    <para>If the <parameter moreinfo="none">security</parameter> parameter is set to
     14    <constant>domain</constant> or <constant>ads</constant>, then this option
     15    <emphasis>should not</emphasis> be used, as the default '*' indicates to Samba
     16    to determine the best DC to contact dynamically, just as all other hosts in an
     17    AD domain do.  This allows the domain to be maintained without modification to
     18    the smb.conf file.  The cryptograpic protection on the authenticated RPC calls
     19    used to verify passwords ensures that this default is safe.</para>
    2120
    22     <para>If parameter is a name, it is looked up using the
    23     parameter <smbconfoption name="name resolve order"/> and so may resolved
    24     by any method and order described in that parameter.</para>
    25 
    26     <para>The password server must be a machine capable of using
    27     the &quot;LM1.2X002&quot; or the &quot;NT LM 0.12&quot; protocol, and it must be in
    28     user level security mode.</para>
    29 
    30     <note><para>Using a password server  means your UNIX box (running
    31     Samba) is only as secure as your  password server. <emphasis>DO NOT
    32     CHOOSE A PASSWORD SERVER THAT  YOU DON'T COMPLETELY TRUST</emphasis>.
    33     </para></note>
    34                
    35     <para>Never point a Samba server at itself for password serving.
    36     This will cause a loop and could lock up your Samba  server!</para>
    37 
    38     <para>The name of the password server takes the standard
    39     substitutions, but probably the only useful one is <parameter moreinfo="none">%m
    40     </parameter>, which means the Samba server will use the incoming
    41     client as the password server. If you use this then you better
    42     trust your clients, and you had better restrict them with hosts allow!</para>
    43 
    44     <para>If the <parameter moreinfo="none">security</parameter> parameter is set to
    45     <constant>domain</constant> or <constant>ads</constant>, then the list of machines in this
    46     option must be a list of Primary or Backup Domain controllers for the
    47     Domain or the character '*', as the Samba server is effectively
    48     in that domain, and will use cryptographically authenticated RPC calls
    49     to authenticate the user logging on. The advantage of using <command moreinfo="none">
    50     security = domain</command> is that if you list several hosts in the
    51     <parameter moreinfo="none">password server</parameter> option then <command moreinfo="none">smbd
    52     </command> will try each in turn till it finds one that responds.  This
    53     is useful in case your primary server goes down.</para>
    54 
    55     <para>If the <parameter moreinfo="none">password server</parameter> option is set
    56     to the character '*', then Samba will attempt to auto-locate the
    57     Primary or Backup Domain controllers to authenticate against by
    58     doing a query for the name <constant>WORKGROUP&lt;1C&gt;</constant>
    59     and then contacting each server returned in the list of IP
    60     addresses from the name resolution source. </para>
     21    <para><emphasis>It is strongly recommended that you use the
     22    default of '*'</emphasis>, however if in your particular
     23    environment you have reason to specify a particular DC list, then
     24    the list of machines in this option must be a list of names or IP
     25    addresses of Domain controllers for the Domain. If you use the
     26    default of '*', or list several hosts in the <parameter
     27    moreinfo="none">password server</parameter> option then <command
     28    moreinfo="none">smbd </command> will try each in turn till it
     29    finds one that responds.  This is useful in case your primary
     30    server goes down.</para>
    6131
    6232    <para>If the list of servers contains both names/IP's and the '*'
    … …  
    6636    this list by locating the closest DC.</para>
    6737               
     38    <para>If parameter is a name, it is looked up using the
     39    parameter <smbconfoption name="name resolve order"/> and so may resolved
     40    by any method and order described in that parameter.</para>
     41
    6842    <para>If the <parameter moreinfo="none">security</parameter> parameter is
    69     set to <constant>server</constant>, then there are different
    70     restrictions that <command moreinfo="none">security = domain</command> doesn't
    71     suffer from:</para>
     43    set to <constant>server</constant>, these additional restrictions apply:</para>
    7244
    7345    <itemizedlist>
    … …  
    8355           
    8456        <listitem>
    85             <para>If you are using a Windows NT server as your
    86             password server then you will have to ensure that your users
     57            <para>You will have to ensure that your users
    8758            are able to login from the Samba server, as when in <command moreinfo="none">
    8859            security = server</command>  mode the network logon will appear to
    89             come from there rather than from the users workstation.</para>
     60            come from the Samba server rather than from the users workstation.</para>
    9061        </listitem>
     62
     63        <listitem>
     64            <para>The client must not select NTLMv2 authentication.</para>
     65        </listitem>
     66
     67        <listitem>
     68          <para>The password server must be a machine capable of using
     69          the &quot;LM1.2X002&quot; or the &quot;NT LM 0.12&quot; protocol, and it must be in
     70          user level security mode.</para>
     71        </listitem>
     72
     73        <listitem>
     74          <para>Using a password server  means your UNIX box (running
     75          Samba) is only as secure as (a host masqurading as) your password server. <emphasis>DO NOT
     76          CHOOSE A PASSWORD SERVER THAT  YOU DON'T COMPLETELY TRUST</emphasis>.
     77          </para>
     78        </listitem>
     79
     80        <listitem>
     81          <para>Never point a Samba server at itself for password serving.
     82          This will cause a loop and could lock up your Samba  server!</para>
     83        </listitem>
     84
     85        <listitem>
     86          <para>The name of the password server takes the standard
     87          substitutions, but probably the only useful one is <parameter moreinfo="none">%m
     88          </parameter>, which means the Samba server will use the incoming
     89          client as the password server. If you use this then you better
     90          trust your clients, and you had better restrict them with hosts allow!</para>
     91        </listitem>
     92
    9193    </itemizedlist>
    9294</description>

  • vendor/current/docs-xml/smbdotconf/security/security.xml

    r414 r740  
    2323    Windows NT.</para>
    2424
    25     <para>The alternatives are <command moreinfo="none">security = share</command>,
    26     <command moreinfo="none">security = server</command> or <command moreinfo="none">security = domain
    27     </command>.</para>
     25    <para>The alternatives are
     26    <command moreinfo="none">security = ads</command> or <command moreinfo="none">security = domain
     27    </command>, which support joining Samba to a Windows domain, along with <command moreinfo="none">security = share</command> and <command moreinfo="none">security = server</command>, both of which are deprecated.</para>
    2828
    2929    <para>In versions of Samba prior to 2.0.0, the default was
    … …  
    3131    the only option at one stage.</para>
    3232
    33     <para>There is a bug in WfWg that has relevance to this
    34     setting. When in user or server level security a WfWg client
    35     will totally ignore the username and password you type in the &quot;connect
    36     drive&quot; dialog box. This makes it very difficult (if not impossible)
    37     to connect to a Samba service as anyone except the user that
    38     you are logged into WfWg as.</para>
    39 
    40     <para>If your PCs use usernames that are the same as their
    41     usernames on the UNIX machine then you will want to use
    42     <command moreinfo="none">security = user</command>. If you mostly use usernames
    43     that don't exist on the UNIX box then use <command moreinfo="none">security =
    44     share</command>.</para>
    45 
    46     <para>You should also use <command moreinfo="none">security = share</command> if you
     33    <para>You should use <command moreinfo="none">security = user</command> and
     34    <smbconfoption name="map to guest"/> if you
    4735    want to mainly setup shares without a password (guest shares). This
    48     is commonly used for a shared printer server. It is more difficult
    49     to setup guest shares with <command moreinfo="none">security = user</command>, see
    50     the <smbconfoption name="map to guest"/> parameter for details.</para>
     36    is commonly used for a shared printer server. </para>
    5137               
    5238    <para>It is possible to use <command moreinfo="none">smbd</command> in a <emphasis>
    … …  
    5743
    5844
     45    <para><anchor id="SECURITYEQUALSUSER"/><emphasis>SECURITY = USER</emphasis></para>
     46
     47    <para>This is the default security setting in Samba.
     48    With user-level security a client must first &quot;log-on&quot; with a
     49    valid username and password (which can be mapped using the <smbconfoption name="username map"/>
     50    parameter). Encrypted passwords (see the <smbconfoption name="encrypted passwords"/> parameter) can also
     51    be used in this security mode. Parameters such as <smbconfoption name="user"/> and <smbconfoption
     52        name="guest only"/> if set      are then applied and
     53    may change the UNIX user to use on this connection, but only after
     54    the user has been successfully authenticated.</para>
     55
     56    <para><emphasis>Note</emphasis> that the name of the resource being
     57    requested is <emphasis>not</emphasis> sent to the server until after
     58    the server has successfully authenticated the client. This is why
     59    guest shares don't work in user level security without allowing
     60    the server to automatically map unknown users into the <smbconfoption name="guest account"/>.
     61    See the <smbconfoption name="map to guest"/> parameter for details on doing this.</para>
     62
     63    <para>See also the section <link linkend="VALIDATIONSECT">NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para>
     64
     65    <para><anchor id="SECURITYEQUALSDOMAIN"/><emphasis>SECURITY = DOMAIN</emphasis></para>
     66
     67    <para>This mode will only work correctly if <citerefentry><refentrytitle>net</refentrytitle>
     68    <manvolnum>8</manvolnum></citerefentry> has been used to add this
     69    machine into a Windows NT Domain. It expects the <smbconfoption name="encrypted passwords"/>
     70        parameter to be set to <constant>yes</constant>. In this
     71    mode Samba will try to validate the username/password by passing
     72    it to a Windows NT Primary or Backup Domain Controller, in exactly
     73    the same way that a Windows NT Server would do.</para>
     74
     75    <para><emphasis>Note</emphasis> that a valid UNIX user must still
     76    exist as well as the account on the Domain Controller to allow
     77    Samba to have a valid UNIX account to map file access to.</para>
     78
     79    <para><emphasis>Note</emphasis> that from the client's point
     80    of view <command moreinfo="none">security = domain</command> is the same
     81    as <command moreinfo="none">security = user</command>. It only
     82    affects how the server deals with the authentication,
     83    it does not in any way affect what the client sees.</para>
     84
     85    <para><emphasis>Note</emphasis> that the name of the resource being
     86    requested is <emphasis>not</emphasis> sent to the server until after
     87    the server has successfully authenticated the client. This is why
     88    guest shares don't work in user level security without allowing
     89    the server to automatically map unknown users into the <smbconfoption name="guest account"/>.
     90    See the <smbconfoption name="map to guest"/> parameter for details on doing this.</para>
     91
     92    <para>See also the section <link linkend="VALIDATIONSECT">
     93    NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para>
     94
     95    <para>See also the <smbconfoption name="password server"/> parameter and
     96         the <smbconfoption name="encrypted passwords"/> parameter.</para>
     97
    5998    <para><anchor id="SECURITYEQUALSSHARE"/><emphasis>SECURITY = SHARE</emphasis></para>
     99
     100    <note><para>This option is deprecated as it is incompatible with SMB2</para></note>
    60101               
    61102    <para>When clients connect to a share level security server, they
    … …  
    136177    NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para>
    137178
    138     <para><anchor id="SECURITYEQUALSUSER"/><emphasis>SECURITY = USER</emphasis></para>
    139 
    140     <para>This is the default security setting in Samba 3.0.
    141     With user-level security a client must first &quot;log-on&quot; with a
    142     valid username and password (which can be mapped using the <smbconfoption name="username map"/>
    143     parameter). Encrypted passwords (see the <smbconfoption name="encrypted passwords"/> parameter) can also
    144     be used in this security mode. Parameters such as <smbconfoption name="user"/> and <smbconfoption
    145         name="guest only"/> if set      are then applied and
    146     may change the UNIX user to use on this connection, but only after
    147     the user has been successfully authenticated.</para>
    148 
    149     <para><emphasis>Note</emphasis> that the name of the resource being
    150     requested is <emphasis>not</emphasis> sent to the server until after
    151     the server has successfully authenticated the client. This is why
    152     guest shares don't work in user level security without allowing
    153     the server to automatically map unknown users into the <smbconfoption name="guest account"/>.
    154     See the <smbconfoption name="map to guest"/> parameter for details on doing this.</para>
    155 
    156     <para>See also the section <link linkend="VALIDATIONSECT">NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para>
    157 
    158     <para><anchor id="SECURITYEQUALSDOMAIN"/><emphasis>SECURITY = DOMAIN</emphasis></para>
    159 
    160     <para>This mode will only work correctly if <citerefentry><refentrytitle>net</refentrytitle>
    161     <manvolnum>8</manvolnum></citerefentry> has been used to add this
    162     machine into a Windows NT Domain. It expects the <smbconfoption name="encrypted passwords"/>
    163         parameter to be set to <constant>yes</constant>. In this
    164     mode Samba will try to validate the username/password by passing
    165     it to a Windows NT Primary or Backup Domain Controller, in exactly
    166     the same way that a Windows NT Server would do.</para>
    167 
    168     <para><emphasis>Note</emphasis> that a valid UNIX user must still
    169     exist as well as the account on the Domain Controller to allow
    170     Samba to have a valid UNIX account to map file access to.</para>
    171 
    172     <para><emphasis>Note</emphasis> that from the client's point
    173     of view <command moreinfo="none">security = domain</command> is the same
    174     as <command moreinfo="none">security = user</command>. It only
    175     affects how the server deals with the authentication,
    176     it does not in any way affect what the client sees.</para>
    177 
    178     <para><emphasis>Note</emphasis> that the name of the resource being
    179     requested is <emphasis>not</emphasis> sent to the server until after
    180     the server has successfully authenticated the client. This is why
    181     guest shares don't work in user level security without allowing
    182     the server to automatically map unknown users into the <smbconfoption name="guest account"/>.
    183     See the <smbconfoption name="map to guest"/> parameter for details on doing this.</para>
    184 
    185     <para>See also the section <link linkend="VALIDATIONSECT">
    186     NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para>
    187 
    188     <para>See also the <smbconfoption name="password server"/> parameter and
    189          the <smbconfoption name="encrypted passwords"/> parameter.</para>
    190 
    191179    <para><anchor id="SECURITYEQUALSSERVER"/><emphasis>SECURITY = SERVER</emphasis></para>
    192180
    193181    <para>
    194         In this mode Samba will try to validate the username/password by passing it to another SMB server, such as an
     182        In this depicted mode Samba will try to validate the username/password by passing it to another SMB server, such as an
    195183        NT box. If this fails it will revert to <command moreinfo="none">security = user</command>. It expects the
    196184        <smbconfoption name="encrypted passwords"/> parameter to be set to <constant>yes</constant>, unless the remote
    … …  
    204192    significant pitfalls since it is more vulnerable to
    205193    man-in-the-middle attacks and server impersonation.  In particular,
    206     this mode of operation can cause significant resource consuption on
     194    this mode of operation can cause significant resource consumption on
    207195    the PDC, as it must maintain an active connection for the duration
    208196    of the user's session.  Furthermore, if this connection is lost,
    209     there is no way to reestablish it, and futher authentications to the
     197    there is no way to reestablish it, and further authentications to the
    210198    Samba server may fail (from a single client, till it disconnects).
     199        </para></note>
     200
     201        <note><para>If the client selects NTLMv2 authentication, then this mode of operation <emphasis>will fail</emphasis>
    211202        </para></note>
    212203
    … …  
    216207    only affects how the server deals  with the authentication, it does
    217208        not in any way affect what the  client sees.</para></note>
     209
     210    <note><para>This option is deprecated, and may be removed in future</para></note>
    218211
    219212    <para><emphasis>Note</emphasis> that the name of the resource being

  • vendor/current/docs-xml/smbdotconf/security/username.xml

    r414 r740  
    1010    each username in turn (left to right).</para>
    1111
    12     <para>The <parameter moreinfo="none">username</parameter> line is needed only when
     12    <para>The deprecated <parameter moreinfo="none">username</parameter> line is needed only when
    1313    the PC is unable to supply its own username. This is the case
    1414    for the COREPLUS protocol or where your users have different WfWg

  • vendor/current/docs-xml/smbdotconf/tuning/strictallocate.xml

    r414 r740  
    1010    of actually forcing the disk system to allocate real storage blocks
    1111    when a file is created or extended to be a given size. In UNIX
    12     terminology this means that Samba will stop creating sparse files.
    13     This can be slow on some systems. When you work with large files like
    14     >100MB or so you may even run into problems with clients running into
    15     timeouts.</para>
     12    terminology this means that Samba will stop creating sparse files.</para>
     13
     14    <para>This option is really desgined for file systems that support
     15    fast allocation of large numbers of blocks such as extent-based file systems.
     16    On file systems that don't support extents (most notably ext3) this can
     17    make Samba slower. When you work with large files over >100MB on file
     18    systems without extents you may even run into problems with clients
     19    running into timeouts.</para>
    1620
    1721    <para>When you have an extent based filesystem it's likely that we can make

  • vendor/current/docs-xml/smbdotconf/winbind/idmapbackend.xml

    r414 r740  
    1212        <para>
    1313        This option specifies the default backend that is used when no special
    14         configuration set by <smbconfoption name="idmap config"/> matches the
    15         specific request.
    16         </para>
    17 
    18         <para>
    19         This default backend also specifies the place where winbind-generated
    20         idmap entries will be stored. So it is highly recommended that you
    21         specify a writable backend like <citerefentry>
    22         <refentrytitle>idmap_tdb</refentrytitle> <manvolnum>8</manvolnum>
    23         </citerefentry> or <citerefentry>
    24         <refentrytitle>idmap_ldap</refentrytitle> <manvolnum>8</manvolnum>
    25         </citerefentry> as the idmap backend. The <citerefentry>
    26         <refentrytitle>idmap_rid</refentrytitle> <manvolnum>8</manvolnum>
    27         </citerefentry> and <citerefentry>
    28         <refentrytitle>idmap_ad</refentrytitle> <manvolnum>8</manvolnum>
    29         </citerefentry> backends are not writable and thus will generate
    30         unexpected results if set as idmap backend.
    31         </para>
    32 
    33         <para>
    34         To use the rid and ad backends, please specify them via the
    35         <smbconfoption name="idmap config"/> parameter, possibly also for the
    36         domain your machine is member of, specified by <smbconfoption
    37         name="workgroup"/>.
    38         </para>
    39 
    40         <para>Examples of SID/uid/gid backends include tdb (<citerefentry>
    41         <refentrytitle>idmap_tdb</refentrytitle><manvolnum>8</manvolnum></citerefentry>),
    42         ldap (<citerefentry><refentrytitle>idmap_ldap</refentrytitle>
    43         <manvolnum>8</manvolnum></citerefentry>), rid (<citerefentry>
    44         <refentrytitle>idmap_rid</refentrytitle><manvolnum>8</manvolnum></citerefentry>),
    45         and ad (<citerefentry><refentrytitle>idmap_ad</refentrytitle>
    46         <manvolnum>8</manvolnum></citerefentry>).
     14        configuration set, but it is now deprecated in favour of the new
     15        spelling <smbconfoption name="idmap config * :  backend"/>.
    4716        </para>
    4817</description>

  • vendor/current/docs-xml/smbdotconf/winbind/idmapconfig.xml

    r414 r740  
    77
    88        <para>
    9         The idmap config prefix provides a means of managing each trusted
    10         domain separately. The idmap config prefix should be followed by the
    11         name of the domain, a colon, and a setting specific to the chosen
    12         backend. There are three options available for all domains:
     9        ID mapping in Samba is the mapping between Windows SIDs and Unix user
     10        and group IDs. This is performed by Winbindd with a configurable plugin
     11        interface. Samba's ID mapping is configured by options starting with the
     12        <smbconfoption name="idmap config"/> prefix.
     13        An idmap option consists of the <smbconfoption name="idmap config"/>
     14        prefix, followed by a domain name or the asterisk character (*),
     15        a colon, and the name of an idmap setting for the chosen domain.
    1316        </para>
    1417
    15         <variablelist> 
     18        <para>
     19        The idmap configuration is hence divided into groups, one group
     20        for each domain to be configured, and one group with the the
     21        asterisk instead of a proper domain name, which speifies the
     22        default configuration that is used to catch all domains that do
     23        not have an explicit idmap configuration of their own.
     24        </para>
     25
     26        <para>
     27        There are three general options available:
     28        </para>
     29
     30        <variablelist>
    1631                <varlistentry>
    1732                <term>backend = backend_name</term>
    1833                <listitem><para>
    19                         Specifies the name of the idmap plugin to use as the
    20                         SID/uid/gid backend for this domain.
     34                This specifies the name of the idmap plugin to use as the
     35                SID/uid/gid backend for this domain. The standard backends are
     36                tdb
     37                (<citerefentry><refentrytitle>idmap_tdb</refentrytitle> <manvolnum>8</manvolnum> </citerefentry>),
     38                tdb2
     39                (<citerefentry><refentrytitle>idmap_tdb2</refentrytitle> <manvolnum>8</manvolnum></citerefentry>),
     40                ldap
     41                (<citerefentry><refentrytitle>idmap_ldap</refentrytitle> <manvolnum>8</manvolnum></citerefentry>),
     42                ,
     43                rid
     44                (<citerefentry><refentrytitle>idmap_rid</refentrytitle> <manvolnum>8</manvolnum></citerefentry>),
     45                ,
     46                hash
     47                (<citerefentry><refentrytitle>idmap_hash</refentrytitle> <manvolnum>8</manvolnum></citerefentry>),
     48                ,
     49                autorid
     50                (<citerefentry><refentrytitle>idmap_autorid</refentrytitle> <manvolnum>8</manvolnum></citerefentry>),
     51                ,
     52                ad
     53                (<citerefentry><refentrytitle>idmap_ad</refentrytitle> <manvolnum>8</manvolnum></citerefentry>),
     54                ,
     55                adex
     56                (<citerefentry><refentrytitle>idmap_adex</refentrytitle> <manvolnum>8</manvolnum></citerefentry>),
     57                ,
     58                and nss.
     59                (<citerefentry><refentrytitle>idmap_nss</refentrytitle> <manvolnum>8</manvolnum></citerefentry>),
     60                The corresponding manual pages contain the details, but
     61                here is a summary.
     62                </para>
     63                <para>
     64                The first three of these create mappings of their own using
     65                internal unixid counters and store the mappings in a database.
     66                These are suitable for use in the default idmap configuration.
     67                The rid and hash backends use a pure algorithmic calculation
     68                to determine the unixid for a SID. The autorid module is a
     69                mixture of the tdb and rid backend. It creates ranges for
     70                each domain encountered and then uses the rid algorithm for each
     71                of these automatically configured domains individually.
     72                The ad and adex
     73                backends both use unix IDs stored in Active Directory via
     74                the standard schema extensions. The nss backend reverses
     75                the standard winbindd setup and gets the unixids via names
     76                from nsswitch which can be useful in an ldap setup.
    2177                </para></listitem>
    2278                </varlistentry>
    … …  
    2480                <varlistentry>
    2581                <term>range = low - high</term>
    26                 <listitem><para>
     82                <listitem><para>
    2783                Defines the available matching uid and gid range for which the
    28                 backend is authoritative.  Note that the range commonly
    29                 matches the allocation range due to the fact that the same
    30                 backend will store and retrieve SID/uid/gid mapping entries.
    31                 </para>
     84                backend is authoritative. For allocating backends, this also
     85                defines the start and the end of the range for allocating
     86                new unid IDs.
     87                </para>
    3288                <para>
    3389                winbind uses this parameter to find the backend that is
    34                 authoritative for a unix ID to SID mapping, so it must be set
    35                 for each individually configured domain, and it must be
    36                 disjoint from the ranges set via <smbconfoption name="idmap
    37                 uid"/> and <smbconfoption name="idmap gid"/>.
     90                authoritative for a unix ID to SID mapping, so it must be set
     91                for each individually configured domain and for the default
     92                configuration. The configured ranges must be mutually disjoint.
    3893                </para></listitem>
     94                </varlistentry>
    3995
     96                <varlistentry>
     97                <term>read only = yes|no</term>
     98                <listitem><para>
     99                This option can be used to turn the writing backends
     100                tdb, tdb2, and ldap into read only mode. This can be useful
     101                e.g. in cases where a pre-filled database exists that should
     102                not be extended automatically.
     103                </para></listitem>
    40104                </varlistentry>
    41105        </variablelist>
    … …  
    44108        The following example illustrates how to configure the <citerefentry>
    45109        <refentrytitle>idmap_ad</refentrytitle> <manvolnum>8</manvolnum>
    46         </citerefentry> for the CORP domain and the
     110        </citerefentry> backend for the CORP domain and the
    47111        <citerefentry><refentrytitle>idmap_tdb</refentrytitle>
    48112        <manvolnum>8</manvolnum></citerefentry> backend for all other
    … …  
    54118
    55119        <programlisting>
    56         idmap backend = tdb
    57         idmap uid = 1000000-1999999
    58         idmap gid = 1000000-1999999
     120        idmap config * : backend = tdb
     121        idmap config * : range = 1000000-1999999
    59122
    60123        idmap config CORP : backend  = ad

  • vendor/current/docs-xml/smbdotconf/winbind/idmapgid.xml

    r414 r740  
    66                <synonym>winbind gid</synonym>
    77<description>
    8         <para>The idmap gid parameter specifies the range of group ids
    9         that are allocated for the purpose of mapping UNX groups to NT group
    10         SIDs. This range of group ids should have no
    11         existing local or NIS groups within it as strange conflicts can
    12         occur otherwise.</para>
    13 
    14         <para>See also the <smbconfoption name="idmap backend"/>, and
    15         <smbconfoption name="idmap config"/> options.
     8        <para>
     9        The idmap gid parameter specifies the range of group ids
     10        for the default idmap configuration. It is now deprecated
     11        in favour of <smbconfoption name="idmap config * : range"/>.
    1612        </para>
    1713
     14        <para>See the <smbconfoption name="idmap config"/> option.</para>
    1815</description>
    1916

  • vendor/current/docs-xml/smbdotconf/winbind/idmapuid.xml

    r414 r740  
    77<description>
    88        <para>
    9         The idmap uid parameter specifies the range of user ids that are
    10         allocated for use in mapping UNIX users to NT user SIDs. This
    11         range of ids should have no existing local
    12         or NIS users within it as strange conflicts can occur otherwise.</para>
     9        The idmap uid parameter specifies the range of user ids for
     10        the default idmap configuration. It is now deprecated in favour
     11        of <smbconfoption name="idmap config * : range"/>.
     12        </para>
    1313
    14         <para>See also the <smbconfoption name="idmap backend"/> and
    15         <smbconfoption name="idmap config"/> options.
    16         </para>
     14        <para>See the <smbconfoption name="idmap config"/> option.</para>
    1715</description>
    1816

  • vendor/current/docs-xml/smbdotconf/winbind/winbindusedefaultdomain.xml

    r414 r740  
    1010        without domain component in their username. Users without a domain
    1111        component are treated as is part of the winbindd server's own
    12         domain. While this does not benifit Windows users, it makes SSH, FTP and
     12        domain. While this does not benefit Windows users, it makes SSH, FTP and
    1313        e-mail function in a way much closer to the way they
    1414        would in a native unix system.</para>
     15        <para>This option should be avoided if possible. It can cause confusion
     16        about responsibilities for a user or group. In many situations it is
     17        not clear whether winbind or /etc/passwd should be seen as authoritative
     18        for a user, likewise for groups.</para>
    1519</description>
    1620

  • vendor/current/docs-xml/using_samba/appc.xml

    r414 r740  
    27292729</refentry>
    27302730
    2731 <refentry id="appc-refentry-194">
    2732 <refmeta>
    2733 <refmiscinfo class="allowable values">YES, NO</refmiscinfo>
    2734 <refmiscinfo class="default">NO</refmiscinfo>
    2735 </refmeta>
    2736 <refnamediv>
    2737 <refname>update encrypted = boolean</refname>
    2738 </refnamediv>
    2739 <refsynopsisdiv>
    2740 <para>Updates the Microsoft-format password file when a user logs in with unencrypted passwords. Provided to ease conversion to encryped passwords for Windows 95/98 and NT. Added in Samba 1.9.18p5.</para>
    2741 
    2742 </refsynopsisdiv>
    2743 </refentry>
    2744 
    27452731<refentry id="appc-refentry-195">
    27462732<refmeta>

  • vendor/current/docs-xml/using_samba/ch06.xml

    r414 r740  
    15931593<row>
    15941594
    1595 <entry colname="col1"><para><literal>update encrypted</literal></para></entry>
    1596 
    1597 <entry colname="col2"><para>boolean</para></entry>
    1598 
    1599 <entry colname="col3"><para>If <literal>yes</literal>, Samba updates the encrypted password file when a client connects to a share with a plaintext password.</para></entry>
    1600 
    1601 <entry colname="col4"><para><literal>no</literal></para></entry>
    1602 
    1603 <entry colname="col5"><para>Global</para></entry>
    1604 
    1605 </row>
    1606 
    1607 <row>
    1608 
    16091595<entry colname="col1"><para><literal>null passwords</literal></para></entry>
    16101596
    … …  
    17701756
    17711757<sect3 role="" label="6.4.4.7" id="ch06-SECT-4.3.7">
    1772 <indexterm id="ch06-idx-969481-0"><primary>pdate encrypted option</primary></indexterm>
    1773 <title>update encrypted</title>
    1774 
    1775 
    1776 <para>For sites switching over to the <indexterm id="ch06-idx-967799-0"><primary>encrypted passwords</primary><secondary>Microsoft format</secondary></indexterm>encrypted password format, Samba provides an option that should help with the transition. The <literal>update</literal> <literal>encrypted</literal> option allows a site to ease into using encrypted passwords from plaintext passwords. You can activate this option as follows:</para>
    1777 
    1778 
    1779 <programlisting>[global]
    1780     update encrypted = yes</programlisting>
    1781 
    1782 
    1783 <para>This instructs Samba to create an encrypted version of each user's Unix password in the <filename>smbpasswd</filename> file each time he or she connects to a share. When this option is enabled, you must have the <literal>encrypt</literal> <literal>passwords</literal> option set to <literal>no</literal> so that the client will pass plaintext passwords to Samba to use to update the files. Once each user has connected at least once, you can set <literal>encrypted</literal> <literal>passwords</literal> <literal>=</literal> <literal>yes</literal>, allowing you to use only the encrypted passwords. The user must already have a valid entry in the <filename>smbpasswd</filename> file for this option to work.</para>
    1784 </sect3>
    1785 
    1786 
    1787 
    1788 <sect3 role="" label="6.4.4.8" id="ch06-SECT-4.3.8">
    17891758<title>null passwords</title>
    17901759
    … …  
    18021771
    18031772
    1804 <sect3 role="" label="6.4.4.9" id="ch06-SECT-4.3.9">
     1773<sect3 role="" label="6.4.4.8" id="ch06-SECT-4.3.8">
    18051774<indexterm id="ch06-idx-969483-0"><primary>smb passwd file option</primary></indexterm>
    18061775<title>
    … …  
    18211790
    18221791
    1823 <sect3 role="" label="6.4.4.10" id="ch06-SECT-4.3.10">
     1792<sect3 role="" label="6.4.4.9" id="ch06-SECT-4.3.9">
    18241793<indexterm id="ch06-idx-969486-0"><primary>hosts equiv option</primary></indexterm>
    18251794<title>
    … …  
    18391808
    18401809
    1841 <sect3 role="" label="6.4.4.11" id="ch06-SECT-4.3.11">
     1810<sect3 role="" label="6.4.4.10" id="ch06-SECT-4.3.10">
    18421811<indexterm id="ch06-idx-969487-0"><primary>use rhosts option</primary></indexterm>
    18431812<title>

  • vendor/current/docs-xml/xslt/man.xsl

    r414 r740  
    2727  <xsl:if test="$content = ''">
    2828    <xsl:apply-templates mode="italic" select="@url" />
    29   </xsl:if>
    30 </xsl:template>
    31 
    32 <xsl:template match="itemizedlist/listitem">
    33   <!-- * We output a real bullet here (rather than, "\(bu", -->
    34   <!-- * the roff bullet) because, when we do character-map -->
    35   <!-- * processing before final output, the character-map will -->
    36   <!-- * handle conversion of the &#x2022; to "\(bu" for us -->
    37   <xsl:text>&#10;</xsl:text>
    38   <xsl:text>.sp</xsl:text>
    39   <xsl:text>&#10;</xsl:text>
    40   <xsl:text>.RS</xsl:text>
    41   <xsl:if test="not($list-indent = '')">
    42     <xsl:text> </xsl:text>
    43     <xsl:value-of select="$list-indent"/>
    44   </xsl:if>
    45   <xsl:text>&#10;</xsl:text>
    46   <!-- * if "n" then we are using "nroff", which means the output is for -->
    47   <!-- * TTY; so we do some fixed-width-font hackery with \h to make a -->
    48   <!-- * hanging indent (instead of using .IP, which has some -->
    49   <!-- * undesirable side effects under certain circumstances) -->
    50   <xsl:call-template name="roff-if-else-start"/>
    51   <xsl:text>\h'-</xsl:text>
    52   <xsl:choose>
    53     <xsl:when test="not($list-indent = '')">
    54       <xsl:text>0</xsl:text>
    55       <xsl:value-of select="$list-indent"/>
    56     </xsl:when>
    57     <xsl:otherwise>
    58       <xsl:text>\n(INu</xsl:text>
    59     </xsl:otherwise>
    60   </xsl:choose>
    61   <xsl:text>'</xsl:text>
    62   <xsl:text>&#x2022;</xsl:text>
    63   <xsl:text>\h'+</xsl:text>
    64   <xsl:choose>
    65     <xsl:when test="not($list-indent = '')">
    66       <xsl:text>0</xsl:text>
    67       <xsl:value-of select="$list-indent - 1"/>
    68     </xsl:when>
    69     <xsl:otherwise>
    70       <xsl:text>\n(INu-1</xsl:text>
    71     </xsl:otherwise>
    72   </xsl:choose>
    73   <xsl:text>'\c&#10;</xsl:text>
    74   <!-- * else, we are not using for "nroff", but instead "troff" - which -->
    75   <!-- * means not for TTY, but for PS or whatever; so we’re not using a -->
    76   <!-- * fixed-width font, so use a real .IP instead -->
    77   <xsl:call-template name="roff-else"/>
    78   <!-- * .IP generates a blank like of space, so let’s go backwards one -->
    79   <!-- * line up to compensate for that -->
    80   <xsl:text>.sp -1&#10;</xsl:text>
    81   <xsl:text>.IP \(bu 2.3&#10;</xsl:text>
    82   <!-- * The value 2.3 is the amount of indentation; we use 2.3 instead -->
    83   <!-- * of 2 because when the font family is New Century Schoolbook it -->
    84   <!-- * seems to require the extra space. -->
    85   <xsl:call-template name="roff-if-end"/>
    86   <xsl:apply-templates/>
    87   <xsl:if test=" following-sibling::listitem">
    88          <xsl:text>&#10;.RE&#10;</xsl:text>
    8929  </xsl:if>
    9030</xsl:template>
Note: See TracChangeset for help on using the changeset viewer.