From d69b4f13f7edda8d8457315936051cc9d3fb103f Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Thu, 9 Dec 2010 16:47:08 +1100 Subject: s3-docs Explain change to NTLMv2 by default in the client --- docs-xml/smbdotconf/security/clientntlmv2auth.xml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'docs-xml') diff --git a/docs-xml/smbdotconf/security/clientntlmv2auth.xml b/docs-xml/smbdotconf/security/clientntlmv2auth.xml index 9f0627abbf..b151df2447 100644 --- a/docs-xml/smbdotconf/security/clientntlmv2auth.xml +++ b/docs-xml/smbdotconf/security/clientntlmv2auth.xml @@ -10,9 +10,9 @@ response. If enabled, only an NTLMv2 and LMv2 response (both much more - secure than earlier versions) will be sent. Many servers + secure than earlier versions) will be sent. Older servers (including NT4 < SP4, Win9x and Samba 2.2) are not compatible with - NTLMv2. + NTLMv2 when not in an NTLMv2 supporting domain Similarly, if enabled, NTLMv1, client lanman auth and 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. + Note that Windows Vista and later versions already use + NTLMv2 by default, and some sites (particularly those following + 'best practice' security polices) only allow NTLMv2 responses, and + not the weaker LM or NTLM. -no +yes -- cgit