1
0
mirror of https://github.com/samba-team/samba.git synced 2025-08-10 21:49:28 +03:00

s3: Fix chained sesssetupAndX/tconn messages

A sesssetupAndX chained with a tconn will not correctly set the TID in
the response header.  I'm seeing an XP client send this chained
sesssetup/tconn when samba has security = share.  Samba's current
behavior is to return a TID of 0 in the smb header rather than the
actual TID.  This patch also updates the UID in the header as well.
This commit is contained in:
Tim Prouty
2009-03-25 00:24:55 +00:00
committed by Jeremy Allison
parent a3873bca51
commit 6c935f95b3

View File

@ -1617,6 +1617,13 @@ void chain_reply(struct smb_request *req)
}
req->outbuf = NULL;
} else {
/*
* Update smb headers where subsequent chained commands
* may have updated them.
*/
SCVAL(req->chain_outbuf, smb_tid, CVAL(req->outbuf, smb_tid));
SCVAL(req->chain_outbuf, smb_uid, CVAL(req->outbuf, smb_uid));
if (!smb_splice_chain(&req->chain_outbuf,
CVAL(req->outbuf, smb_com),
CVAL(req->outbuf, smb_wct),