[cifs-protocol] [REG:113100910848319] [MS-SMB2]Q 2 of 3: Does the client behaviour stated in section 3.2.5.4 (Receiving an SMB2 LOGOFF Response) apply in case of an error as well?

Bryan Burgin bburgin at microsoft.com
Tue Oct 8 22:18:26 MDT 2013


Thread for:

SR 113100910848319
[MS-SMB2]Q 2 of 3: Does the client behaviour stated in section 3.2.5.4 (Receiving an SMB2 LOGOFF Response) apply in case of an error as well?

Bryan

-----Original Message-----
From: Bryan Burgin 
Sent: Tuesday, October 8, 2013 9:14 PM
To: 'Shirish Pargaonkar'
Cc: cifs-protocol at samba.org
Subject: RE: session logoff request / response clarification

Shirish,

Thank you for your questions.  To track these issues, we created three cases to track each one separately.  Please do not respond to this mail; I will start a new thread for each.  An engineer from the Protocols will contact you soon. The case numbers are below:

SR 113100910848314:
[MS-SMB2] Q 1 of 3: Types of error a server can return in response to a session logoff request from a client (section 2.2.8).

SR 113100910848319
[MS-SMB2]Q 2 of 3: Does the client behaviour stated in section 3.2.5.4 (Receiving an SMB2 LOGOFF Response) apply in case of an error as well?

SR 113100910848322:
[MS-SMB2] Q 3 of 3: behaviour if the signature verification fails in section 3.2.5.1.3

Bryan




-----Original Message-----
From: Shirish Pargaonkar [mailto:shirishpargaonkar at gmail.com] 
Sent: Tuesday, October 8, 2013 5:53 PM
To: Interoperability Documentation Help
Cc: cifs-protocol at samba.org
Subject: session logoff request / response clarification

---
Would like to have a clarification in MS-SMB2 document about the

1) Types of error a server can return in response to a session logoff
   request from a client (section 2.2.8).

2) The state of the session and expected client behaviour when a server
   returns an error to a session logoff request.
   Specifically, does the client behaviour stated in section 3.2.5.4
   (Receiving an SMB2 LOGOFF Response) apply in case of an error as well?

3) There is no verbiage about server behaviour if the signature verification
   fails the way it is described for client behaviour if the signature
   verification fails in section 3.2.5.1.3.
   In the context of session logoff request, if the signature does not match,
   what is the correct/expected server behaviour?
   Right now, in SMB3 dialect, Windows 8 server returns a response with an
   error (access denied) for a missing/mismatched signature.  Is that correct
   or should a server discard the request and do no further processing for it?

---
MS-CIFS document lists the types of error a server may return in response to a session logoff request (section 2.2.4.54.2) but it does not state the state of the smb session and expected client behaviour in case of an error received in logoff response in section 3.2.5.1.
In case of signature mismatch in the context of session logoff request, Windows 8 server for smb1 dialect, behaves in a similar way as above (smb3).


More information about the cifs-protocol mailing list