[cifs-protocol] MS-NLMP and V1 Signatuers without Extended Session Security
idra at samba.org
Sat Oct 19 16:06:20 MDT 2013
I'd like some clarifications about sections 3.4.4 and 18.104.22.168 of
Section 3.4.4 details how to create a signature in the absence of
Extended Session Security Negotiation.
The description of the operation is confusing and it seem not in line
with 3 different Open Source implementations I have inspected.
In particular the documentation seem to imply the signature is created
by RC4 of the concatenation of (Random_Pad, CRC32(Message), 0x00000000)
all 4 bytes values, then discarding the first 4 bytes of the resulting
ciphertext and replacing them with a 0 (last operation) and discarding
the last 4 bytes of the ciphertext and replacing them with the XOR of a
Sequence Number, and keeping only the central 4 bytes of the Ciphertext
as the Checksum.
The Open Source implementations I inspected instead create the signature
by RC4 of the concatenation of (0x00000000, CRC32(Message), SeqNum),
some of them replace the fist 4 bytes with a random value/random_pad or
None of them XOR the Sequence Number.
It is unclear to me what implementation is right, and Section 22.214.171.124
where a protocol Example is provided lacks the necessary data for
reproducing the test.
In particular the Section does not make clear what Key is used to
initialize the RC4 cipher (Later sections 126.96.36.199 and 188.8.131.52 both do).
There is also perhaps a terminology problem. In the paragraph a NONCE
(set to zero) is mentioned, I assume this is the RandomPad described in
3.4.3, if so using a consistent terminology would be useful.
Finally 184.108.40.206 does not show the full signature buffer sent back to the
peer. Both sections 220.127.116.11 and 18.104.22.168 instead do.
Could you please clarify the algorithm in 3.4.3, use consistent
terminology between 3.4.3 and 22.214.171.124 and provide sufficient data to
verify 126.96.36.199 ?
More information about the cifs-protocol