summaryrefslogtreecommitdiff
path: root/docs/smbdotconf/security/lanmanauth.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/smbdotconf/security/lanmanauth.xml')
-rw-r--r--docs/smbdotconf/security/lanmanauth.xml31
1 files changed, 31 insertions, 0 deletions
diff --git a/docs/smbdotconf/security/lanmanauth.xml b/docs/smbdotconf/security/lanmanauth.xml
new file mode 100644
index 0000000000..dba8d6f975
--- /dev/null
+++ b/docs/smbdotconf/security/lanmanauth.xml
@@ -0,0 +1,31 @@
+<samba:parameter name="lanman auth"
+ context="G"
+ type="boolean"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>This parameter determines whether or not <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> will attempt to authenticate users
+ using the LANMAN password hash. If disabled, only clients which support NT
+ password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not
+ Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.</para>
+
+ <para>The LANMAN encrypted response is easily broken, due to it's
+ case-insensitive nature, and the choice of algorithm. Servers
+ without Windows 95/98 or MS DOS clients are advised to disable
+ this option. </para>
+
+ <para>Unlike the <command moreinfo="none">encypt
+ passwords</command> option, this parameter cannot alter client
+ behaviour, and the LANMAN response will still be sent over the
+ network. See the <command moreinfo="none">client lanman
+ auth</command> to disable this for Samba's clients (such as smbclient)</para>
+
+ <para>If this option, and <command moreinfo="none">ntlm
+ auth</command> are both disabled, then only NTLMv2 logins will be
+ permited. Not all clients support NTLMv2, and most will require
+ special configuration to us it.</para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>