summaryrefslogtreecommitdiff
path: root/source3/smbd/sesssetup.c
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2012-02-26 16:49:09 +0100
committerVolker Lendecke <vl@samba.org>2012-03-10 15:34:11 +0100
commit90b33a05e967e9e29c4584bed188ef6fa5a3fbf0 (patch)
tree52b88ef421378abe267a39486c07335c90b2308b /source3/smbd/sesssetup.c
parenta28a740f5805e0bd766cedaa581066c6e9b15e3a (diff)
downloadsamba-90b33a05e967e9e29c4584bed188ef6fa5a3fbf0.tar.gz
samba-90b33a05e967e9e29c4584bed188ef6fa5a3fbf0.tar.bz2
samba-90b33a05e967e9e29c4584bed188ef6fa5a3fbf0.zip
s3: Make sure the andX chains are ended correctly
Normally chain_reply took care of this. This will go away soon.
Diffstat (limited to 'source3/smbd/sesssetup.c')
-rw-r--r--source3/smbd/sesssetup.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/source3/smbd/sesssetup.c b/source3/smbd/sesssetup.c
index b2e1f2421f..cc801364cd 100644
--- a/source3/smbd/sesssetup.c
+++ b/source3/smbd/sesssetup.c
@@ -736,6 +736,9 @@ void reply_sesssetup_and_X(struct smb_request *req)
/* it's ok - setup a reply */
reply_outbuf(req, 3, 0);
+ SSVAL(req->outbuf, smb_vwv0, 0xff); /* andx chain ends */
+ SSVAL(req->outbuf, smb_vwv1, 0); /* no andx offset */
+
if (get_Protocol() >= PROTOCOL_NT1) {
push_signature(&req->outbuf);
/* perhaps grab OS version here?? */