Hi Andreas, My suggestion below was rejected as inappropriate for section 2, since it isn't a MUST rule. In fact, it is felt that the documentation covers the issue as the server processing rules for every SMB2 command (except NEGOTIATE and SESSION_SETUP) specify verifying the SessionId with the single exception of ECHO. We don't document what isn't done, just what we do. By implication, SessionID can be 0 for ECHO (unless the message is signed).
Hope that helps! Best regards, Jeff McCashland | Senior Escalation Engineer | Microsoft Protocol Open Specifications Team Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada) Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300 We value your feedback. My manager is Rama Ganesan (ramagane), +1 (425) 703-8712 -----Original Message----- From: Andreas Schneider [mailto:a...@samba.org] Sent: Monday, July 31, 2017 1:19 AM To: Jeff McCashland <je...@microsoft.com> Cc: cifs-protocol <cifs-protocol@lists.samba.org>; MSSolve Case Email <casem...@microsoft.com> Subject: Re: SR# 117072516091337 :SMB2 ECHO request On Thursday, 27 July 2017 21:25:51 CEST Jeff McCashland wrote: > Hi Andreas, Hi Jeff, > Normally, this type of information would go into the processing rules > for the Client (Section 3.2). However, the gist of what I explained > below is that SMB2 doesn't have any rules for the client to process > the ECHO command. The client is free to use and process ECHO as > needed, as long as the structure in section 2.2 is met. > > We could add something like: > > 2.2.1.1 SMB2 Packet Header - ASYNC > SessionId (8 bytes): Uniquely identifies the established session for > the command. This field MUST be set to 0 for an SMB2 NEGOTIATE Request > (section > 2.2.3) and for an SMB2 NEGOTIATE Response (section 2.2.4). SessionId > MAY be set to 0 for an SMB2 ECHO Request (section 2.2.28) and for an > SMB2 ECHO Response (section 2.2.29). > > 2.2.1.2 SMB2 Packet Header - SYNC > SessionId (8 bytes): Uniquely identifies the established session for > the command. This field MUST be set to 0 for an SMB2 NEGOTIATE Request > (section > 2.2.3) and for an SMB2 NEGOTIATE Response (section 2.2.4). SessionId > MAY be set to 0 for an SMB2 ECHO Request (section 2.2.28) and for an > SMB2 ECHO Response (section 2.2.29). > > Would that be helpful? I think that's perfect. Thanks, Andreas -- Andreas Schneider GPG-ID: CC014E3D Samba Team a...@samba.org https://na01.safelinks.protection.outlook.com/?url=www.samba.org&data=04%7C01%7Cjeffm%40microsoft.com%7Cd36f9158e9b64939726f08d4d7ecc685%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636370859323974707%7CUnknown%7CVW5rbm93bnx7IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT3RoZXIifQ%3D%3D%7C-1&sdata=r1tOj%2BsAyNPTMwrewvIJZvrRkEnmHzHc%2Fm%2FQDiOST8Y%3D&reserved=0 _______________________________________________ cifs-protocol mailing list cifs-protocol@lists.samba.org https://lists.samba.org/mailman/listinfo/cifs-protocol