Günther,
I should have waited a few seconds longer as I just received feedback from the
product group. Below are your questions and answers. Updates will be made to
the technical documents in a future refresh. Please let me know if this
resolves your questions.
Thank you for your patience.
Bryan
Q1: Is CountOutgoingAuthInfos defining the number of CurrentOutgoingAuthInfos
*and* PreviousOutgoingAuthInfos in total, n-times both structs or just n-times
CurrentOutgoingAuthInfos ? In any case, is it up the user to figure out the
number of PreviousOutgoingAuthInfos from calculation with the offsets ?
(likewise for CountIncomingAuthInfos and CurrentIncomingAuthInfos and
PreviousIncomingAuthInfos)
A: PreviousOutgoingAuthInfos is either an array of 0 elements or an array of
exactly the same number of elements as CurrentOutgoingAuthInfos (this number is
CountOutgoingAuthInfos). Same applies to CountIncomingAuthInfos and
CurrentIncomingAuthInfos and PreviousIncomingAuthInfos
Q2: "CountIncomingAuthInfos": is there a typo ? It says: "Specifies the count
of entries present in the CountIncomingAuthInfos field"
A: Yes, It should say "Specifies the count of entries present in the
CurrentIncomingAuthInfos field"
Q3: Which values do ByteOffsetCurrentOutgoingAuthInfo and
ByteOffsetPreviousOutgoingAuthInfo have in case CountOutgoingAuthInfos is 0 ?
(likewise for ByteOffsetCurrentIncomingAuthInfo and
ByteOffsetPreviousIncomingAuthInfo and CountIncomingAuthInfos)
A: ByteOffsetCurrentOutgoingAuthInfo will always be 12
([CountOutgoingAuthInfos][ByteOffsetCurrentOutgoingAuthInfo][ByteOffsetPreviousAuthInfos])
as it points to where the CurrentOutgoingAuthInfo array begins (which remains
the same irrespective of how many entries are in the array).
In this case (when CountOutgoingAuthInfos is 0),
ByteOffsetPreviousOutgoingAuthInfo will also be 12 as it points to where the
PreviousOutgoingAuthInfo array begins (which is
ByteOffsetCurrentOutgoingAuthInfo + size of CurrentIncomingAuthInfos and the
latter is 0).
-----Original Message-----
From: Bryan Burgin
Sent: Thursday, October 07, 2010 2:03 PM
To: Guenther Deschner ([email protected])
Cc: MSSolve Case Email
Subject: RE: [REG:110092949275537] MS-LSAD 2.2.7.16
LSAPR_TRUSTED_DOMAIN_AUTH_BLOB
Günther,
Just a quick update. I am expecting a reply from development very soon. As
soon as I have a solution for you I'll pass it on.
Bryan
-----Original Message-----
From: Bryan Burgin
Sent: Wednesday, September 29, 2010 10:19 AM
To: Guenther Deschner ([email protected])
Cc: MSSolve Case Email
Subject: [REG:110092949275537] MS-LSAD 2.2.7.16 LSAPR_TRUSTED_DOMAIN_AUTH_BLOB
[Darryl Welch, Will Gregg, Eric Urbasich on bcc, FYI] [Note to case: Guenther
and the core Samba team are working with us in-person at a Interop Lab
engagement]
Guenther,
I am reviewing this for you and will be making a request to improve the
document. The case to track this issue is SR 110092949275537.
Bryan
-----Original Message-----
From: Guenther Deschner [mailto:[email protected]]
Sent: Tuesday, September 28, 2010 10:44 AM
To: Darryl Welch
Subject: MS-LSAD 2.2.7.16 LSAPR_TRUSTED_DOMAIN_AUTH_BLOB
Hi Darryl,
here are some questions for clarification for the
LSAPR_TRUSTED_DOMAIN_AUTH_BLOB struct as defined in MS-LSAD 2.2.7.16:
* Is CountOutgoingAuthInfos defining the number of CurrentOutgoingAuthInfos
*and* PreviousOutgoingAuthInfos in total, n-times both structs or just n-times
CurrentOutgoingAuthInfos ? In any case, is it up the user to figure out the
number of PreviousOutgoingAuthInfos from calculation with the offsets ?
(likewise for CountIncomingAuthInfos and CurrentIncomingAuthInfos and
PreviousIncomingAuthInfos)
* "CountIncomingAuthInfos": is there a typo ? It says: "Specifies the count of
entries present in the CountIncomingAuthInfos field"
* Which values do ByteOffsetCurrentOutgoingAuthInfo and
ByteOffsetPreviousOutgoingAuthInfo have in case CountOutgoingAuthInfos is 0 ?
(likewise for ByteOffsetCurrentIncomingAuthInfo and
ByteOffsetPreviousIncomingAuthInfo and CountIncomingAuthInfos)
Thanks,
Guenther
--
Günther Deschner GPG-ID: 8EE11688
Red Hat [email protected]
Samba Team [email protected]
_______________________________________________
cifs-protocol mailing list
[email protected]
https://lists.samba.org/mailman/listinfo/cifs-protocol
