[cifs-protocol] [REG:119072621001605] [MS-SMB2] 126.96.36.199.4 SMB2_NETNAME_NEGOTIATE_CONTEXT_ID
bburgin at microsoft.com
Fri Jul 26 17:12:27 UTC 2019
[Dochelp to bcc]
Thank you for your question. We created SR 119072621001605 to track this issue. An engineer will contact you soon.
From: Stefan Metzmacher <metze at samba.org>
Sent: Friday, July 26, 2019 1:23 AM
To: Interoperability Documentation Help <dochelp at microsoft.com>; cifs-protocol at lists.samba.org
Subject: [MS-SMB2] 188.8.131.52.4 SMB2_NETNAME_NEGOTIATE_CONTEXT_ID
I just noticed a documentation bug in
[MS-SMB2] 184.108.40.206.4 SMB2_NETNAME_NEGOTIATE_CONTEXT_ID:
NetName (variable): A null-terminated Unicode string containing the
server name and specified by the client application.
Windows Server 1903 sends the name without null-termination, see the attached capture.
I just contacted dochelp for this and noticed (from reading the code) that the kernel sends null-termination for the SMB2_NETNAME_NEGOTIATE_CONTEXT_ID value.
I think you should fix that and backport it to stable releases, it would be good if all clients would implement it like windows.
I implemented it for Samba here:
More information about the cifs-protocol