Good morning Mr. French. Thank you for reporting the OS and NOS string
documentation shortcomings in [MS-SMB2].
I have created case SRX090617600092 for your comments concerning that, and
expect to begin work on this later today, or tomorrow morning at the latest.
I confirm that a documentation change is currently pending (work in progress)
against the raw ('Implicit NTLM') NTLMSSP buffer content. I will be glad to
update you when we have the final text ready.
Regards,
Bill Wesse
MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
TEL: +1(980) 776-8200
CELL: +1(704) 661-5438
FAX: +1(704) 665-9606
-----Original Message-----
From: Steve French [mailto:smfre...@gmail.com]
Sent: Wednesday, June 17, 2009 9:14 AM
To: Interoperability Documentation Help
Cc: p...@tridgell.net; cifs-proto...@samba.org
Subject: Re: [Pfif] erroneous references to little-endian
In implementing SMB2 Session Setup protocol support I did not notice
reference to the "OS" and "NOS" (the strings which name the operating
system and network operating system version fields of the client and
server) which followed the security blob. See sections 2.2.5 and
2.2.6 of MS-SMB2 and 3.3.5.5. The description of the "buffer" field
just notes that it "MUST contain a token as produced by the GSS
protocol as specified in section 3.2.5.3" (which would not describe
the operating system or network operating system fields). Note that
an earlier CAR shows that the description of the buffer field is
incorrect in another way (Windows servers accept NTLMSSP, not
encapsulated in GSS in the buffer field for SMB2, and in some ways
that is easier and safer to generate).
--
Thanks,
Steve
_______________________________________________
cifs-protocol mailing list
cifs-protocol@cifs.org
https://lists.samba.org/mailman/listinfo/cifs-protocol
