From a482b3e14ec4e3eada9c2477c9eae2bfbe017f53 Mon Sep 17 00:00:00 2001 From: Andreas Schneider Date: Thu, 29 Jul 2010 13:18:35 +0200 Subject: s3-auth: Remove docs about obsolete 'update encrypted' option. --- docs-xml/using_samba/ch06.xml | 37 +++---------------------------------- 1 file changed, 3 insertions(+), 34 deletions(-) (limited to 'docs-xml/using_samba/ch06.xml') diff --git a/docs-xml/using_samba/ch06.xml b/docs-xml/using_samba/ch06.xml index e0973b6cc8..b099e96071 100644 --- a/docs-xml/using_samba/ch06.xml +++ b/docs-xml/using_samba/ch06.xml @@ -1592,20 +1592,6 @@ Password changed for user dave -update encrypted - -boolean - -If yes, Samba updates the encrypted password file when a client connects to a share with a plaintext password. - -no - -Global - - - - - null passwords boolean @@ -1769,23 +1755,6 @@ password level -pdate encrypted option -update encrypted - - -For sites switching over to the encrypted passwordsMicrosoft formatencrypted password format, Samba provides an option that should help with the transition. The update encrypted option allows a site to ease into using encrypted passwords from plaintext passwords. You can activate this option as follows: - - -[global] - update encrypted = yes - - -This instructs Samba to create an encrypted version of each user's Unix password in the smbpasswd file each time he or she connects to a share. When this option is enabled, you must have the encrypt passwords option set to no 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 encrypted passwords = yes, allowing you to use only the encrypted passwords. The user must already have a valid entry in the smbpasswd file for this option to work. - - - - - null passwords @@ -1801,7 +1770,7 @@ password level - + smb passwd file option smb passwd file @@ -1820,7 +1789,7 @@ smb passwd file - + hosts equiv option hosts equiv @@ -1838,7 +1807,7 @@ hosts equiv - + use rhosts option use rhosts -- cgit