[MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3

  • Article

This topic lists Errata found in [MS-SMB2] since it was last published. Since this topic is updated frequently, we recommend that you subscribe to this RSS feed to receive update notifications.

Errata are subject to the same terms as the Open Specifications documentation referenced.

RSS

To view a PDF file of the errata for the previous versions of this document, see the following ERRATA Archives:

March 4, 2020 - Download

August 24, 2020 – Download

April 7, 2021 - Download

June 1, 2021 - Download

October 6, 2021 - Download

April 29, 2022 – Download

Errata below are for Protocol Document Version V67.0 – 2023/02/27.

Errata Published*

Description

2023/05/22

In section 3.2.5.2, "Receiving an SMB2 Negotiate Response," revised the processing rule for the SecurityMode field to indicate that it is part of the Negotiate Response rather than the SMB2 header.

Changed from:

If the SecurityMode field in the SMB2 header of the response has the SMB2_NEGOTIATE_SIGNING_REQUIRED bit set, the client MUST set Connection.RequireSigning to TRUE.

Changed to:

If the SecurityMode field in the Negotiate Response has the SMB2_NEGOTIATE_SIGNING_REQUIRED bit set, the client MUST set Connection.RequireSigning to TRUE.

2023/04/11

In section 2.2.14, "SMB2 CREATE Response," added a condition for using the SMB2_CREATE_FLAG_REPARSEPOINT in the Flags field:

Changed from:

Value

Meaning

SMB2_CREATE_FLAG_REPARSEPOINT

0x01

When set, indicates the last portion of the file path is a reparse point.

Changed to:

Value

Meaning

SMB2_CREATE_FLAG_REPARSEPOINT

0x01

When set, indicates the last portion of the file path is a reparse point. This MUST be used when the last component of a file opened is a reparse point, and the create request Create Options do not contain FILE_OPEN_REPARSE_POINT.

In section 3.3.5.9, "Receiving an SMB2 CREATE Request," added a condition for creating a reparse point when Open.Local is a reparse point but there is no FILE_OPEN_REPARSE_POINT value in the Create Options:

Changed from:

If Connection.Dialect belongs to the SMB 3.x dialect family and Open.LocalOpen is a reparse point, set the SMB2_CREATE_FLAG_REPARSEPOINT bit in the Flags field.

Changed to:

If Connection.Dialect belongs to the SMB 3.x dialect family and Open.LocalOpen is a reparse point, and the create request Create Options do not contain FILE_OPEN_REPARSE_POINT, set the SMB2_CREATE_FLAG_REPARSEPOINT bit in the Flags field.

*Date format: YYYY/MM/DD