we weren't filling in the keylength in LANMAN1 and LANMAN2.1 negprot

reply. Seems to have been broken for a long time!

diff --git a/source/smbd/negprot.c b/source/smbd/negprot.c
index db0694a840447758bea3170fae7c365c7a07e38c..66cd8352400d55cc679b005b13bdf9fdc62303ab 100644 (file)
--- a/source/smbd/negprot.c
+++ b/source/smbd/negprot.c
@@ -100,6 +100,7 @@ static int reply_lanman1(char *inbuf, char *outbuf)
        SSVAL(outbuf,smb_vwv1,secword); 
        /* Create a token value and add it to the outgoing packet. */
        if (global_encrypted_passwords_negotiated) {
+               SSVAL(outbuf,smb_vwv11, 8);
                get_challenge(smb_buf(outbuf));
        }
 
@@ -143,6 +144,7 @@ static int reply_lanman2(char *inbuf, char *outbuf)
 
        /* Create a token value and add it to the outgoing packet. */
        if (global_encrypted_passwords_negotiated) {
+               SSVAL(outbuf,smb_vwv11, 8);
                get_challenge(smb_buf(outbuf));
        }