• S
    NTLM auth and sign - Use appropriate server challenge · d3ba50b1
    Shirish Pargaonkar 提交于
    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: NShirish Pargaonkar <shirishpargaonkar@gmail.com>
    Signed-off-by: NSteve French <sfrench@us.ibm.com>
    d3ba50b1
sess.c 28.6 KB