MS-GPEF unclear definition of a field
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
MS-GPEF unclear definition of a field
by ronnie sahlberg
::
Rate this Message:
|
|
|
RE: MS-GPEF unclear definition of a field
by John Dunning-5
::
Rate this Message:
|
|
|
RE: MS-GPEF unclear definition of a field
by Edgar Olougouna
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Hi Ronnie, I have completed my research on your questions regarding the
[MS-GPEF] document. As we agreed, I will then proceed and close the case. This is a summary of the answers. Document MS-GPEF section 2.2.1.2.1 -------------------------------------------------------- The efsblob starts with a 32 bit integer called reserved. The text further describes the field as : Reserved (4 bytes): Reserved. MUST be set to 0x01 0x00
0x01 0x00. It is unclear from this description what the byte order
should be. I.e. should this field be encoded as 0x01000100 or 0x00010001 Please enhance this section so it is clearer on what
value this 32 bit field should have. Answer: ------- The reserved field at the beginning of the Efsblob packet
is a byte array. The bytes 0x01, 0x00, 0x01, and 0x00 must be sent as bytes in
the order specified. The change will be reflected in an upcoming release: Reserved (4
bytes): Reserved array of bytes. MUST be set to 0x01 0x00 0x01
0x00, in that order. Section 2.2.1.2.2 ------------------------- In one trace I have of this blob there is a 4 byte
integer with the value 0x00000001 between the Reserved2 field and the first
byte of the SID. Is this a field that is missing in the documentation? Answer: ------- The Reserved2 field is defined as an 8 byte-field. And we
agreed through clarification emails that the SID is starting at the correct
offset. Thanks for helping us improve the [MS-GPEF] specification. Best regards, Edgar A. Olougouna Sr. SEE, Microsoft DSC Protocol Team | Email:
edgaro@... | Tel: +1.469.775.7189 x 57189 -----Original Message----- Hi, I am a pfif subcontractor. Document MS-GPEF section 2.2.1.2.1 -------------------------------------------------------- The efsblob starts with a 32 bit integer called reserved. The text further describes the field as : Reserved (4 bytes): Reserved. MUST be set to 0x01 0x00
0x01 0x00. It is unclear from this description what the byte order
should be. I.e. should this field be encoded as 0x01000100 or 0x00010001 Please enhance this section so it is clearer on what
value this 32 bit field should have. Section 2.2.1.2.2 ------------------------- In one trace I have of this blob there is a 4 byte
integer with the value 0x00000001 between the Reserved2 field and the
first byte of the SID. Is this a field that is missing in the documentation? regards ronnie sahlberg _______________________________________________ cifs-protocol mailing list cifs-protocol@... https://lists.samba.org/mailman/listinfo/cifs-protocol |
|
|
RE: MS-GPEF unclear definition of a field
by John Dunning-5
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Looks good to me. John From: Edgar Olougouna Hi Ronnie, I have completed my research on your questions regarding the
[MS-GPEF] document. As we agreed, I will then proceed and close the case. This is a summary of the answers. Document MS-GPEF section 2.2.1.2.1 -------------------------------------------------------- The efsblob starts with a 32 bit integer called reserved. The text further describes the field as : Reserved (4 bytes): Reserved. MUST be set to 0x01 0x00
0x01 0x00. It is unclear from this description what the byte order
should be. I.e. should this field be encoded as 0x01000100 or 0x00010001 Please enhance this section so it is clearer on what
value this 32 bit field should have. Answer: ------- The reserved field at the beginning of the Efsblob packet
is a byte array. The bytes 0x01, 0x00, 0x01, and 0x00 must be sent as bytes in
the order specified. The change will be reflected in an upcoming release: Reserved (4
bytes): Reserved array of bytes. MUST be set to 0x01 0x00 0x01
0x00, in that order. Section 2.2.1.2.2 ------------------------- In one trace I have of this blob there is a 4 byte
integer with the value 0x00000001 between the Reserved2 field and the first
byte of the SID. Is this a field that is missing in the documentation? Answer: ------- The Reserved2 field is defined as an 8 byte-field. And we
agreed through clarification emails that the SID is starting at the correct
offset. Thanks for helping us improve the [MS-GPEF] specification. Best regards, Edgar A. Olougouna Sr. SEE, Microsoft DSC Protocol Team | Email:
edgaro@... | Tel: +1.469.775.7189 x 57189 -----Original Message----- Hi, I am a pfif subcontractor. Document MS-GPEF section 2.2.1.2.1 -------------------------------------------------------- The efsblob starts with a 32 bit integer called reserved. The text further describes the field as : Reserved (4 bytes): Reserved. MUST be set to 0x01 0x00
0x01 0x00. It is unclear from this description what the byte order
should be. I.e. should this field be encoded as 0x01000100 or 0x00010001 Please enhance this section so it is clearer on what
value this 32 bit field should have. Section 2.2.1.2.2 ------------------------- In one trace I have of this blob there is a 4 byte
integer with the value 0x00000001 between the Reserved2 field and
the first byte of the SID. Is this a field that is missing in the documentation? regards ronnie sahlberg _______________________________________________ cifs-protocol mailing list cifs-protocol@... https://lists.samba.org/mailman/listinfo/cifs-protocol |
| Free Forum Powered by Nabble | Forum Help |
