2004-04-07 14:15:11 +04:00
<samba:parameter name= "lanman auth"
context="G"
2015-05-01 00:32:45 +03:00
type="boolean"
2017-07-03 05:11:47 +03:00
function="_lanman_auth"
2019-09-05 02:23:22 +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 02:23:22 +03:00
<para > This parameter has been deprecated since Samba 4.11 and
support for LanMan (as distinct from NTLM, NTLMv2 or
Kerberos authentication)
will be removed in a future Samba release.</para>
<para > That is, in the future, the current default of
<command > lanman auth = no</command>
will be the enforced behaviour.</para>
2004-04-07 14:15:11 +04:00
<para > This parameter determines whether or not <citerefentry > <refentrytitle > smbd</refentrytitle>
2004-12-23 05:18:53 +03:00
<manvolnum > 8</manvolnum> </citerefentry> will attempt to
authenticate users or permit password changes
2004-04-07 14:15:11 +04:00
using the LANMAN password hash. If disabled, only clients which support NT
2004-12-23 05:18:53 +03:00
password hashes (e.g. Windows NT/2000 clients, smbclient, but not
Windows 95/98 or the MS DOS network client) will be able to
connect to the Samba host.</para>
2004-04-07 14:15:11 +04:00
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. Servers
2004-12-23 05:18:53 +03:00
without Windows 95/98/ME or MS DOS clients are advised to disable
2004-04-07 14:15:11 +04:00
this option. </para>
2009-10-02 19:55:50 +04:00
<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
2015-07-27 00:02:57 +03:00
auth is re-enabled later on.
2009-10-02 19:55:50 +04:00
</para>
2004-04-07 14:15:11 +04:00
2019-06-01 00:04:48 +03:00
<para > Unlike the <parameter moreinfo= "none" > encrypt
passwords</parameter> option, this parameter cannot alter client
2004-04-07 14:15:11 +04:00
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>
2019-08-29 22:54:14 +03:00
<para > This parameter is overridden by <parameter moreinfo= "none" > ntlm
2019-06-01 00:04:48 +03:00
auth</parameter> , so unless that it is also set to
<constant > ntlmv1-permitted</constant> or <constant > yes</constant> ,
2019-08-29 23:42:36 +03:00
then only NTLMv2 logins will be permitted and no LM hash will be
2019-06-01 00:04:48 +03:00
stored. All modern clients support NTLMv2, and but some older
clients require special configuration to use it.</para>
2022-03-25 02:18:01 +03:00
<para > <emphasis > This parameter has no impact on the Samba AD DC,
LM authentication is always disabled and no LM password is ever
stored.</emphasis> </para>
2004-04-07 14:15:11 +04:00
</description>
2007-09-10 06:51:19 +04:00
<value type= "default" > no</value>
2004-04-07 14:15:11 +04:00
</samba:parameter>