Ignore:
Timestamp:
May 12, 2014, 8:58:38 PM (11 years ago)
Author:
Silvan Scherrer
Message:

Samba 3.6: updated vendor to latest version

Location:
vendor/current/docs-xml
Files:
2 added
1 deleted
6 edited

Legend:

Unmodified
Added
Removed
  • vendor/current/docs-xml/build/DTD/samba.entities

    r746 r860  
    181181
    182182<para>Note that specifying this parameter here will
    183 override the <smbconfoption><name>log level</name></smbconfoption> parameter
     183override the <smbconfoption name="log level" /> parameter
    184184in the &smb.conf; file.</para>
    185185</listitem>
     
    208208
    209209<para>Note that specifying this parameter here will
    210 override the <smbconfoption><name>log level</name></smbconfoption> parameter
     210override the <smbconfoption name="log level" /> parameter
    211211in the &smb.conf; file.</para>
    212212</listitem>
     
    298298<para>If this parameter is not set then the name resolve order
    299299defined in the &smb.conf; file parameter 
    300 (<smbconfoption><name>name resolve order</name></smbconfoption>) will be used.
     300(<smbconfoption name="name resolve order" />) will be used.
    301301</para>
    302302
    303303<para>The default order is lmhosts, host, wins, bcast. Without
    304 this parameter or any entry in the <smbconfoption><name>name resolve order</name></smbconfoption> parameter of the &smb.conf; file, the name
     304this parameter or any entry in the
     305<smbconfoption name="name resolve order" /> parameter of
     306the &smb.conf; file, the name
    305307resolution methods will be attempted in this order. </para></listitem>
    306308</varlistentry>'>
     
    311313<listitem><para>This option allows you to override
    312314the NetBIOS name that Samba uses for itself. This is identical
    313 to setting the <smbconfoption><name>netbios name</name></smbconfoption> parameter in the &smb.conf; file.
     315to setting the <smbconfoption name="netbios name" /> parameter in
     316the &smb.conf; file.
    314317However, a command
    315318line setting will take precedence over settings in
  • vendor/current/docs-xml/manpages-3/idmap_ad.8.xml

    r740 r860  
    2323        extensions. This module implements only the &quot;idmap&quot;
    2424        API, and is READONLY. Mappings must be provided in advance
    25         by the administrator by adding the posixAccount/posixGroup
    26         classes and relative attribute/value pairs to the user and
    27         group objects in the AD.</para>
     25        by the administrator by adding the uidNumber attributes for
     26        users and gidNumber attributes for groups in the AD. Winbind
     27        will only map users that have a uidNumber and whose primary
     28        group have a gidNumber attribute set. It is however
     29        recommended that all groups in use have gidNumber attributes
     30        assigned, otherwise they are not working.</para>
    2831
    2932        <para>
  • vendor/current/docs-xml/manpages-3/ntlm_auth.1.xml

    r746 r860  
    161161                <variablelist>
    162162                  <varlistentry>
    163                   <term>Username</term>
    164                  
    165                 <listitem><para>The username, expected to be in
    166                 Samba's <smbconfoption name="unix charset"/>.
    167                 </para>
    168 
    169                       <para><example>Username: bob</example></para>
    170                       <para><example>Username:: Ym9i</example></para>
    171                     </listitem></varlistentry>
    172 
    173                   <varlistentry>
    174                   <term>NT-Domain</term>
    175                 <listitem><para>The user's domain, expected to be in
    176                 Samba's <smbconfoption name="unix charset"/>.
    177                 </para>
    178 
    179                       <para><example>NT-Domain: WORKGROUP</example></para>
    180                       <para><example>NT-Domain:: V09SS0dST1VQ</example></para>
    181                     </listitem></varlistentry>
    182 
    183                   <varlistentry>
    184                   <term>Full-Username</term>
    185                 <listitem><para>The fully qualified username, expected to be in
    186                 Samba's <smbconfoption name="unix charset"/> and qualified with the
    187                 <smbconfoption name="winbind separator"/>.
    188                 </para>
    189 
    190                       <para><example>Full-Username: WORKGROUP\bob</example></para>
    191                       <para><example>Full-Username:: V09SS0dST1VQYm9i</example></para>
    192                     </listitem></varlistentry>
    193 
    194                   <varlistentry>
    195                   <term>LANMAN-Challenge</term>
    196                  
    197                 <listitem><para>The 8 byte <command>LANMAN Challenge</command> value,
    198                 generated randomly by the server, or (in cases such as
    199                 MSCHAPv2) generated in some way by both the server and
    200                 the client.
    201                 </para>
    202                       <para><example>LANMAN-Challenge: 0102030405060708</example></para>
    203                     </listitem></varlistentry>
    204 
    205                   <varlistentry>
    206                   <term>LANMAN-Response</term>
    207                  
    208                 <listitem><para>The 24 byte <command>LANMAN Response</command> value,
    209                 calculated from the user's password and the supplied
    210                 <command>LANMAN Challenge</command>.  Typically, this
    211                 is provided over the network by a client wishing to authenticate.
    212                 </para>
    213                       <para><example>LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</example></para>
    214 
    215                     </listitem></varlistentry>
    216 
    217                   <varlistentry>
    218                   <term>NT-Response</term>
    219                 <listitem><para>The >= 24 byte <command>NT Response</command>
    220                 calculated from the user's password and the supplied
    221                 <command>LANMAN Challenge</command>.  Typically, this is
    222                 provided over the network by a client wishing to authenticate.
    223                  </para>       
    224                       <para><example>NT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</example></para>
    225 
    226                     </listitem></varlistentry>
    227 
    228                   <varlistentry>
    229                   <term>Password</term>
    230                 <listitem><para>The user's password.  This would be
    231                 provided by a network client, if the helper is being
    232                 used in a legacy situation that exposes plaintext
    233                 passwords in this way.
    234                  </para>       
    235                       <para><example>Password: samba2</example></para>
    236                       <para><example>Password:: c2FtYmEy</example></para>
    237 
    238                     </listitem></varlistentry>
    239 
    240                   <varlistentry>
    241                   <term>Request-User-Session-Key</term>
    242                 <listitem><para>Upon successful authenticaiton, return
    243                 the user session key associated with the login.
    244                  </para>       
    245                       <para><example>Request-User-Session-Key: Yes</example></para>
    246 
    247                     </listitem></varlistentry>
    248 
    249                   <varlistentry>
    250                   <term>Request-LanMan-Session-Key</term>
    251                 <listitem><para>Upon successful authenticaiton, return
    252                 the LANMAN session key associated with the login.
    253                  </para>       
    254                       <para><example>Request-LanMan-Session-Key: Yes</example></para>
    255 
    256                     </listitem></varlistentry>
    257 
    258                 <para><warning>Implementers should take care to base64 encode
    259                 any data (such as usernames/passwords) that may contain malicous user data, such as
    260                 a newline.  They may also need to decode strings from
    261                 the helper, which likewise may have been base64 encoded.</warning></para>
    262         </variablelist>
    263 
     163                    <term>Username</term>
     164                    <listitem><para>The username, expected to be in
     165                    Samba's <smbconfoption name="unix charset"/>.
     166                    </para>
     167                    <varlistentry>
     168                      <term>Examples:</term>
     169                      <para>Username: bob</para>
     170                      <para>Username:: Ym9i</para>
     171                    </varlistentry>
     172                    </listitem>
     173                  </varlistentry>
     174
     175                  <varlistentry>
     176                    <term>NT-Domain</term>
     177                    <listitem><para>The user's domain, expected to be in
     178                    Samba's <smbconfoption name="unix charset"/>.
     179                    </para>
     180
     181                    <varlistentry>
     182                      <term>Examples:</term>
     183                      <para>NT-Domain: WORKGROUP</para>
     184                      <para>NT-Domain:: V09SS0dST1VQ</para>
     185                    </varlistentry>
     186                    </listitem>
     187                  </varlistentry>
     188
     189                  <varlistentry>
     190                    <term>Full-Username</term>
     191                    <listitem><para>The fully qualified username, expected to be
     192                    in Samba's <smbconfoption name="unix charset"/> and qualified
     193                    with the <smbconfoption name="winbind separator"/>.</para>
     194                    <varlistentry>
     195                      <term>Examples:</term>
     196                      <para>Full-Username: WORKGROUP\bob</para>
     197                      <para>Full-Username:: V09SS0dST1VQYm9i</para>
     198                    </varlistentry>
     199                    </listitem>
     200                  </varlistentry>
     201
     202                  <varlistentry>
     203                    <term>LANMAN-Challenge</term>
     204                    <listitem><para>The 8 byte <command>LANMAN Challenge</command>
     205                    value, generated randomly by the server, or (in cases such
     206                    as MSCHAPv2) generated in some way by both the server and
     207                    the client.</para>
     208                    <varlistentry>
     209                      <term>Examples:</term>
     210                      <para>LANMAN-Challenge: 0102030405060708</para>
     211                    </varlistentry>
     212                    </listitem>
     213                  </varlistentry>
     214
     215                  <varlistentry>
     216                    <term>LANMAN-Response</term>
     217                    <listitem><para>The 24 byte <command>LANMAN Response</command> value,
     218                    calculated from the user's password and the supplied
     219                    <command>LANMAN Challenge</command>.  Typically, this
     220                    is provided over the network by a client wishing to authenticate.
     221                    </para>
     222                    <varlistentry>
     223                      <term>Examples:</term>
     224                      <para>LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</para>
     225                    </varlistentry>
     226                    </listitem>
     227                  </varlistentry>
     228
     229                  <varlistentry>
     230                    <term>NT-Response</term>
     231                    <listitem><para>The >= 24 byte <command>NT Response</command>
     232                    calculated from the user's password and the supplied
     233                    <command>LANMAN Challenge</command>.  Typically, this is
     234                    provided over the network by a client wishing to authenticate.
     235                    </para>
     236                    <varlistentry>
     237                      <term>Examples:</term>
     238                      <para>NT-Response: 0102030405060708090A0B0C0D0E0F10111213141516171</para>
     239                      </varlistentry>
     240                    </listitem>
     241                  </varlistentry>
     242
     243                  <varlistentry>
     244                    <term>Password</term>
     245                    <listitem><para>The user's password.  This would be
     246                    provided by a network client, if the helper is being
     247                    used in a legacy situation that exposes plaintext
     248                    passwords in this way.</para>
     249                    <varlistentry>
     250                      <term>Examples:</term>
     251                      <para>Password: samba2</para>
     252                      <para>Password:: c2FtYmEy</para>
     253                    </varlistentry>
     254                    </listitem>
     255                  </varlistentry>
     256
     257                  <varlistentry>
     258                    <term>Request-User-Session-Key</term>
     259                    <listitem><para>Upon successful authenticaiton, return
     260                    the user session key associated with the login.</para>
     261                    <varlistentry>
     262                      <term>Examples:</term>
     263                      <para>Request-User-Session-Key: Yes</para>
     264                    </varlistentry>
     265                    </listitem>
     266                  </varlistentry>
     267
     268                  <varlistentry>
     269                    <term>Request-LanMan-Session-Key</term>
     270                    <listitem><para>Upon successful authenticaiton, return
     271                    the LANMAN session key associated with the login.
     272                    </para>
     273                    <varlistentry>
     274                      <term>Examples:</term>
     275                      <para>Request-LanMan-Session-Key: Yes</para>
     276                    </varlistentry>
     277                    </listitem>
     278                  </varlistentry>
     279
     280                </variablelist>
    264281                </listitem>
    265282                </varlistentry>
    266         </variablelist>
    267         </listitem>
     283                </variablelist>
     284                  <warning><para>Implementers should take care to base64 encode
     285                  any data (such as usernames/passwords) that may contain malicous user data, such as
     286                  a newline. They may also need to decode strings from
     287                  the helper, which likewise may have been base64 encoded.</para></warning>
     288                </listitem>
    268289      </varlistentry>
    269290     
  • vendor/current/docs-xml/manpages-3/vfs_catia.8.xml

    r740 r860  
    3232        <para>The Catia CAD package commonly creates filenames that
    3333        use characters that are illegal in CIFS filenames. The
    34         <command>vfs_catia</command> VFS module implements a fixed character
     34        <command>vfs_catia</command> VFS module implements a character
    3535        mapping so that these files can be shared with CIFS clients.
    3636        </para>
    3737
    3838        <para>This module is stackable.</para>
     39
     40        <para>Up to samba version 3.4.x a fixed character mapping was used.
     41        The invalid windows characters  \ / : * ? " &lt; &gt; | and the blank
     42        character were mapped in a hardcoded way.
     43        </para>
     44
     45        <para>Starting with samba-3.5.0 a more flexible mapping was introduced.
     46        The new parameter "catia:mappings" now specifies the mapping on a char by char
     47        basis using the notation: unix hex char 0x.. : windows hex char 0x..
     48        Multiple character mappings are separated by a comma.
     49        </para>
     50
    3951
    4052</refsect1>
     
    4456        <title>EXAMPLES</title>
    4557
     58        <para>Samba versions up to 3.4.x:</para>
    4659        <para>Map Catia filenames on the [CAD] share:</para>
    4760
     
    5265</programlisting>
    5366
     67        <para>Samba versions 3.5.0 and later:</para>
     68        <para>Map Catia filenames on the [CAD] share:</para>
     69
     70<programlisting>
     71        <smbconfsection name="[CAD]"/>
     72        <smbconfoption name="path">/data/cad</smbconfoption>
     73        <smbconfoption name="vfs objects">catia</smbconfoption>
     74        <smbconfoption name="catia:mappings">0x22:0xa8</smbconfoption>
     75</programlisting>
     76
     77        <para>To get the full formerly fixed mappings:</para>
     78<programlisting>
     79        <smbconfsection name="[CAD]"/>
     80        <smbconfoption name="path">/data/cad</smbconfoption>
     81        <smbconfoption name="vfs objects">catia</smbconfoption>
     82        <smbconfoption name="catia:mappings">0x22:0xa8,0x2a:0xa4,0x2f:0xf8,0x3a:0xf7,0x3c:0xab,0x3e:0xbb,0x3f:0xbf,0x5c:0xff,0x7c:0xa6,0x20:0xb1</smbconfoption>
     83</programlisting>
     84
     85        <para>Unix filename to be translated (Note that the path delimiter "/" is not used here):
     86        </para>
     87        <para>a\a:a*a?a"a&lt;a&gt;a|a a</para>
     88
     89        <para>Resulting windows filename:</para>
     90
     91        <para>a&#x00ff;a&#x00f7;a&#x00a4;a&#x00bf;a&#x00a8;a&#x00ab;a&#x00bb;a&#x00a6;a&#x00b1;a
     92        </para>
     93
     94        <para>Note that the character mapping must work in BOTH directions
     95        (unix -&gt; windows and windows -&gt; unix) to get unique and existing file names!
     96        </para>
     97
     98        <para>A NOT working example:</para>
     99
     100<programlisting>
     101        <smbconfsection name="[CAD]"/>
     102        <smbconfoption name="path">/data/cad</smbconfoption>
     103        <smbconfoption name="vfs objects">catia</smbconfoption>
     104        <smbconfoption name="catia:mappings">0x3a:0x5f</smbconfoption>
     105</programlisting>
     106
     107         <para>Here the colon ":" is mapped to the underscore "_".</para>
     108         <para>Assuming a unix filename "a:should_work", which is well translated
     109         to windows as "a_should_work".</para>
     110         <para>BUT the reverse mapping from windows "a_should_work" to unix
     111         will result in "a:should:work" - something like "file not found"
     112         will be returned.
     113         </para>
     114
    54115</refsect1>
    55116
     
    57118        <title>VERSION</title>
    58119
    59         <para>This man page is correct for version 3.0.25 of the Samba suite.
     120        <para>This man page is correct for all versions up to 4.0.3 of the Samba suite.
    60121        </para>
    61122</refsect1>
     
    68129        by the Samba Team as an Open Source project similar
    69130        to the way the Linux kernel is developed.</para>
     131        <para>New version written by Guenter Kukkukk kukks@samba.org</para>
    70132
    71133</refsect1>
  • vendor/current/docs-xml/manpages-3/vfs_crossrename.8.xml

    r740 r860  
    3838        manual copy and delete operations. If the rename by copy is done by the
    3939        server this can be much more efficient. vfs_crossrename tries to do
    40         this server-side cross-device rename operation. There are however
    41         limitations that this module currently does not solve:
     40        this server-side cross-device rename operation.
     41        </para>
     42
     43        <para>There are however limitations that this module currently does not
     44        solve:</para>
    4245
    4346        <variablelist>
    4447                <varlistentry>
    45                 the ACLs of files are not preserved
     48                <para>The ACLs of files are not preserved,</para>
    4649                </varlistentry>
    4750                <varlistentry>
    48                 meta data in EAs are not preserved
     51                <para>meta data in EAs are not preserved,</para>
    4952                </varlistentry>
    5053                <varlistentry>
    51                 renames of whole subdirectories cannot be done recursively,
     54                <para>renames of whole subdirectories cannot be done recursively,
    5255                in that case we still return STATUS_NOT_SAME_DEVICE and
    53                 let the client decide what to do
     56                let the client decide what to do,</para>
    5457                </varlistentry>
    5558                <varlistentry>
    56                 rename operations of huge files can cause hangs on the
     59                <para>rename operations of huge files can cause hangs on the
    5760                client because clients expect a rename operation to
    58                 return fast
     61                return fast.</para>
    5962                </varlistentry>
    6063        </variablelist>
    61         </para>
    6264
    6365        <para>This module is stackable.</para>
  • vendor/current/docs-xml/smbdotconf/protocol/maxprotocol.xml

    r414 r860  
    3636        <listitem>
    3737            <para><constant>SMB2</constant>: Re-implementation of the SMB protocol.
    38             Used by Windows Vista and newer. The Samba implementation of SMB2 is
    39             currently marked experimental!</para>
     38            Used by Windows Vista and newer.</para>
    4039        </listitem>
    4140    </itemizedlist>
Note: See TracChangeset for help on using the changeset viewer.