From 2f4f2890e5919e52f66ac72d572e020a9c556dba Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Sat, 5 Jul 2003 01:50:16 +0000 Subject: Update from Andrew Bartlett with documentation for 'client lanman auth' and 'client ntlmv2 auth' (This used to be commit 60f0934a6dc7a34dad42ba86744a1e3426e99967) --- .../smbdotconf/security/clientntlmv2auth.xml | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 docs/docbook/smbdotconf/security/clientntlmv2auth.xml (limited to 'docs/docbook/smbdotconf/security/clientntlmv2auth.xml') diff --git a/docs/docbook/smbdotconf/security/clientntlmv2auth.xml b/docs/docbook/smbdotconf/security/clientntlmv2auth.xml new file mode 100644 index 0000000000..4e60613a3e --- /dev/null +++ b/docs/docbook/smbdotconf/security/clientntlmv2auth.xml @@ -0,0 +1,26 @@ + + + This parameter determines whether or not smbclient + 8 will attempt to + authenticate itself to servers using the NTLMv2 encrypted password + response. + + If enabled, only an NTLMv2 and LMv2 response (both much more + secure than earlier versions) will be sent. Many servers + (including NT4 < SP4, Win9x and Samba 2.2) are not compatible with + NTLMv2. + + If disabled, an NTLM response (and possibly a LANMAN response) + will be sent by the client, depending on the value of client lanman auth. + + Note that some sites (particularly + those following 'best practice' security polices) only allow NTLMv2 + responses, and not the weaker LM or NTLM. + + Default : ntlmv2 auth = no + + -- cgit