Changeset 745 for trunk/server/docs-xml/using_samba/ch06.xml
- Timestamp:
- Nov 27, 2012, 4:43:17 PM (13 years ago)
- Location:
- trunk/server
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/server
- Property svn:mergeinfo changed
/vendor/current merged: 581,587,591,594,597,600,615,618,740
- Property svn:mergeinfo changed
-
trunk/server/docs-xml/using_samba/ch06.xml
r414 r745 1593 1593 <row> 1594 1594 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 1609 1595 <entry colname="col1"><para><literal>null passwords</literal></para></entry> 1610 1596 … … 1770 1756 1771 1757 <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">1789 1758 <title>null passwords</title> 1790 1759 … … 1802 1771 1803 1772 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"> 1805 1774 <indexterm id="ch06-idx-969483-0"><primary>smb passwd file option</primary></indexterm> 1806 1775 <title> … … 1821 1790 1822 1791 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"> 1824 1793 <indexterm id="ch06-idx-969486-0"><primary>hosts equiv option</primary></indexterm> 1825 1794 <title> … … 1839 1808 1840 1809 1841 <sect3 role="" label="6.4.4.1 1" id="ch06-SECT-4.3.11">1810 <sect3 role="" label="6.4.4.10" id="ch06-SECT-4.3.10"> 1842 1811 <indexterm id="ch06-idx-969487-0"><primary>use rhosts option</primary></indexterm> 1843 1812 <title>
Note:
See TracChangeset
for help on using the changeset viewer.