summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBjörn Jacke <bj@sernet.de>2009-10-02 17:55:50 +0200
committerBjörn Jacke <bj@sernet.de>2009-10-03 00:22:51 +0200
commit2aacca010da59c2521bddda3e004271008fe2b6f (patch)
tree7845fe1916adc0beede638a6eebec0fd19a2e385
parent2b9b232912a6e561e0f5ba57afbd605dc4197d97 (diff)
downloadsamba-2aacca010da59c2521bddda3e004271008fe2b6f.tar.gz
samba-2aacca010da59c2521bddda3e004271008fe2b6f.tar.bz2
samba-2aacca010da59c2521bddda3e004271008fe2b6f.zip
s3:doc: add some detail about lanman auth parameter
add interesting detail: lm passwords will be removed from databaѕe with lanman auth = no
-rw-r--r--docs-xml/smbdotconf/security/lanmanauth.xml7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs-xml/smbdotconf/security/lanmanauth.xml b/docs-xml/smbdotconf/security/lanmanauth.xml
index 4e68c5e03a..e055bd35f1 100644
--- a/docs-xml/smbdotconf/security/lanmanauth.xml
+++ b/docs-xml/smbdotconf/security/lanmanauth.xml
@@ -16,6 +16,13 @@
case-insensitive nature, and the choice of algorithm. Servers
without Windows 95/98/ME or MS DOS clients are advised to disable
this option. </para>
+
+ <para>When this parameter is set to <value>no</value> this
+ will also result in sambaLMPassword in Samba's passdb being
+ blanked after the next password change. As a result of that
+ lanman clients won't be able to authenticate, even if lanman
+ auth is reenabled later on.
+ </para>
<para>Unlike the <command moreinfo="none">encrypt
passwords</command> option, this parameter cannot alter client