blob: 60e1c86809e24a4bb805e742db4e83f73296938d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
<samba:parameter name="client lanman auth"
context="G"
type="boolean"
deprecated="1"
xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
<description>
<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>
<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 its
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.</para>
</description>
<value type="default">no</value>
</samba:parameter>
|
