[cifs-protocol] FW: Question about self relative form of SECURITY_DESCRIPTOR (SRX091118600013)
Bill Wesse
billwe at microsoft.com
Wed Nov 18 05:59:26 MST 2009
-----Original Message-----
From: Bill Wesse
Sent: Wednesday, November 18, 2009 7:57 AM
To: Nadezhda Ivanova; Interoperability Documentation Help
Cc: cifs-protocols at samba.org
Subject: RE: Question about self relative form of SECURITY_DESCRIPTOR (SRX091118600013)
Good morning Nadya! I will begin work on this for you this morning. I have created the below case:
SRX091118600013 [MS-DTYP] 2.4.6 self relative form of SECURITY_DESCRIPTOR
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: Nadezhda Ivanova [mailto:nadezhda.ivanova at postpath.com]
Sent: Wednesday, November 18, 2009 6:26 AM
To: Interoperability Documentation Help
Cc: cifs-protocols at samba.org
Subject: Question about self relative form of SECURITY_DESCRIPTOR
Hello,
In MS-DTYP, section 2.4.6 (the table on page 55), the self relative format of a security descriptor is described as follows:
Revision
Sbz1
Control
OffsetOwner
OffsetGroup
OffsetSacl
OffsetDacl
OwnerSid
GroupSid
Sacl
Dacl
However, what we receive from the wire from a Win2003 or Win2008 is in fact in the form:
Revision
Sbz1
Control
OffsetOwner
OffsetGroup
OffsetSacl
OffsetDacl
Sacl
Dacl
OwnerSid
GroupSid
Although it does not prevent parsing the security descriptor, on a binary level the encoding between Windows and Samba is different, because Samba's is as documented. Is this the desired behavior or something that will be fixed?
Best Regards,
Nadezhda Ivanova
More information about the cifs-protocol
mailing list