| commit | b6c86e1ef28d9008eec1d39ad714a475dc735c38 | |
| author | Tim Prouty <tprouty@samba.org> | |
| Wed, 25 Mar 2009 00:24:55 +0000 (25 00:24 +0000) | ||
| committer | Jeremy Allison <jra@samba.org> | |
| Sat, 9 May 2009 00:10:13 +0000 (8 17:10 -0700) | ||
| tree | 377d86cdd97ab246c956a49d6a493a62948cd539 | treesnapshot (tar.gz zip) |
| parent | 3f55201564afae5681b3530cb767da7f2b64794c | commitdiff |
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.
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.
| source3/smbd/process.c | diffblobblamehistory |