2004-04-07 14:15:11 +04:00
<samba:parameter name= "client lanman auth"
context="G"
2015-05-01 00:32:45 +03:00
type="boolean"
2019-09-05 07:53:46 +03:00
deprecated="1"
2005-03-13 01:41:20 +03:00
xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
2004-04-07 14:15:11 +04:00
<description >
2019-09-05 07:53:46 +03:00
<para > This parameter has been deprecated since Samba 4.13 and
support for LanMan (as distinct from NTLM, NTLMv2 or
Kerberos) authentication as a client
will be removed in a future Samba release.</para>
<para > That is, in the future, the current default of
<command > client NTLMv2 auth = yes</command>
will be the enforced behaviour.</para>
2004-04-07 14:15:11 +04:00
<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>
2009-02-20 11:20:16 +03:00
<para > The LANMAN encrypted response is easily broken, due to its
2004-04-07 14:15:11 +04:00
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
2009-02-27 13:09:59 +03:00
moreinfo="none">client plaintext auth</command> option.</para>
2004-04-07 14:15:11 +04:00
<para > Likewise, if the <command moreinfo= "none" > client ntlmv2
auth</command> parameter is enabled, then only NTLMv2 logins will be
attempted.</para>
</description>
2007-09-10 06:51:19 +04:00
<value type= "default" > no</value>
2004-04-07 14:15:11 +04:00
</samba:parameter>