summaryrefslogtreecommitdiff
path: root/source3/libsmb/clifile.c
diff options
context:
space:
mode:
authorTim Prouty <tprouty@samba.org>2009-03-25 00:24:55 +0000
committerJeremy Allison <jra@samba.org>2009-05-08 17:09:16 -0700
commit6c935f95b3d4aaf0922c5a7baf59c1e8224c019a (patch)
tree1013585af050b0318768a89ef99a8e26804400fd /source3/libsmb/clifile.c
parenta3873bca516e0f89302409c89910561707360d14 (diff)
downloadsamba-6c935f95b3d4aaf0922c5a7baf59c1e8224c019a.tar.gz
samba-6c935f95b3d4aaf0922c5a7baf59c1e8224c019a.tar.bz2
samba-6c935f95b3d4aaf0922c5a7baf59c1e8224c019a.zip
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.
Diffstat (limited to 'source3/libsmb/clifile.c')
0 files changed, 0 insertions, 0 deletions