Ignore:
Timestamp:
Nov 27, 2012, 4:43:17 PM (13 years ago)
Author:
Silvan Scherrer
Message:

Samba Server: updated trunk to 3.6.0

Location:
trunk/server
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/server

  • trunk/server/docs-xml/using_samba/ch06.xml

    r414 r745  
    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>
Note: See TracChangeset for help on using the changeset viewer.