[cifs-protocol] data checksum value in FRS

Sebastian Canevari Sebastian.Canevari at microsoft.com
Thu Nov 17 18:12:43 MST 2011


Hi Matthieu,

Thanks for your question.

Someone on our team will follow up with you shortly.

Regards,

Sebastian


Sebastian Canevari | Escalation Engineer | US-CSS Developer Support Core (DSC) Protocol Team
P +1 469 775 7849 
One Microsoft Way, 98052, Redmond, WA, USA http://support.microsoft.com


-----Original Message-----
From: cifs-protocol-bounces at cifs.org [mailto:cifs-protocol-bounces at cifs.org] On Behalf Of Matthieu Patou
Sent: Thursday, November 17, 2011 3:48 PM
To: cifs-protocol at samba.org; pfif at tridgell.net; Interoperability Documentation Help
Subject: [cifs-protocol] data checksum value in FRS

Hello Dochelp,

Paragraph 2.2.3.7DATA_EXTENSION_CHECKSUM of MS-FRS1 indiciate about the data checksum:

Data: MUST be a 128-bit MD5 digest of staging file and attributes, as specified in [RFC1321].
See section 2.2.3.10 for how the MD5 digest is constructed on a staging file and attributes.

Section 2.2.3.10 didn't bring much more information, but it seems while looking at a replication (initial + regular) between 2 DCs that the checksum attribute is sometime omitted (it's 16 null bytes).

Like in packet 3286 in the attached trace.

At the opposite in packet 5300 we have a non null checksum, can you explain in which case the checksum can or must be null ?

The trace is attached to this email.

Thanks.

Matthieu.


--
Matthieu Patou
Samba Team
http://samba.org



More information about the cifs-protocol mailing list