summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/security/clientlanmanauth.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/docbook/smbdotconf/security/clientlanmanauth.xml')
-rw-r--r--docs/docbook/smbdotconf/security/clientlanmanauth.xml28
1 files changed, 0 insertions, 28 deletions
diff --git a/docs/docbook/smbdotconf/security/clientlanmanauth.xml b/docs/docbook/smbdotconf/security/clientlanmanauth.xml
deleted file mode 100644
index a427198ea3..0000000000
--- a/docs/docbook/smbdotconf/security/clientlanmanauth.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-<samba:parameter name="client lanman auth"
- context="G"
- advanced="1" developer="1"
- xmlns:samba="http://samba.org/common">
-<listitem>
- <para>This parameter determines whether or not <citerefentry><refentrytitle>smbclient</refentrytitle>
- <manvolnum>8</manvolnum></citerefentry> and other samba client
- tools will attempt to authenticate itself to servers using the
- weaker LANMAN password hash. If disabled, only server which support NT
- password hashes (e.g. Windows NT/2000, Samba, etc... but not
- Windows 95/98) will be able to be connected from the Samba client.</para>
-
- <para>The LANMAN encrypted response is easily broken, due to it's
- case-insensitive nature, and the choice of algorithm. Clients
- without Windows 95/98 servers are advised to disable
- this option. </para>
-
- <para>Disabling this option will also disable the <command
- moreinfo="none">client plaintext auth</command> option</para>
-
- <para>Likewise, if the <command moreinfo="none">client ntlmv2
- auth</command> parameter is enabled, then only NTLMv2 logins will be
- attempted. Not all servers support NTLMv2, and most will require
- special configuration to us it.</para>
-
- <para>Default : <command moreinfo="none">client lanman auth = yes</command></para>
-</listitem>
-</samba:parameter>