From 37866df4ee51e2bf62d26be9d87a22d94106a95a Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Thu, 3 May 2012 15:52:41 +0200 Subject: [PATCH] s3:smbd: use reply_force_doserror(req, ERRSRV, ERRbaduid) on SMBulogoff We don't support security = share anymore, so we should always have a valid session. Found by the raw.context test. metze Autobuild-User: Stefan Metzmacher Autobuild-Date: Wed May 23 12:47:37 CEST 2012 on sn-devel-104 --- source3/smbd/reply.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/source3/smbd/reply.c b/source3/smbd/reply.c index b93052ade2c..d01ff905a37 100644 --- a/source3/smbd/reply.c +++ b/source3/smbd/reply.c @@ -2085,6 +2085,11 @@ void reply_ulogoffX(struct smb_request *req) if(vuser == NULL) { DEBUG(3,("ulogoff, vuser id %d does not map to user.\n", req->vuid)); + + req->vuid = UID_FIELD_INVALID; + reply_force_doserror(req, ERRSRV, ERRbaduid); + END_PROFILE(SMBulogoffX); + return; } /* in user level security we are supposed to close any files -- 2.11.4.GIT