removing docs from HEAD

(This used to be commit 820903ef5a062b4b9824c33ee035c68a39c8eeb0)

1 files changed, 0 insertions, 30 deletions

diff --git a/docs/docbook/smbdotconf/security/lanmanauth.xml b/docs/docbook/smbdotconf/security/lanmanauth.xml
deleted file mode 100644
index 0a8fdd3ef3..0000000000
--- a/docs/docbook/smbdotconf/security/lanmanauth.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-<samba:parameter name="lanman auth"
-                 context="G"
-                 advanced="1" developer="1"
-                 xmlns:samba="http://samba.org/common">
-<listitem>
-    <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>
-
-    <para>Default : <command moreinfo="none">lanman auth = yes</command></para>
-</listitem>
-</samba:parameter>