commit d3ba50b17aa7a391bb5b3dcd8d6ba7a02c4f031c
author Shirish Pargaonkar <shirishpargaonkar@gmail.com> Wed Oct 27 15:20:36 2010 -0500
committer Steve French <sfrench@us.ibm.com> Fri Oct 29 01:47:30 2010 +0000
tree 452ddaeb1d52387a852d0c3cf46c4253347d0a27
parent 6b03590412c977ae8fa1635c9b80854ab19a5b78

NTLM auth and sign - Use appropriate server challenge

Need to have cryptkey or server challenge in smb connection
(struct TCP_Server_Info) for ntlm and ntlmv2 auth types for which
cryptkey (Encryption Key) is supplied just once in Negotiate Protocol
response during an smb connection setup for all the smb sessions over
that smb connection.

For ntlmssp, cryptkey or server challenge is provided for every
smb session in type 2 packet of ntlmssp negotiation, the cryptkey
provided during Negotiation Protocol response before smb connection
does not count.

Rename cryptKey to cryptkey and related changes.

Signed-off-by: Shirish Pargaonkar <shirishpargaonkar@gmail.com>
Signed-off-by: Steve French <sfrench@us.ibm.com>