On Tue, 2008-06-10 at 12:31 -0700, Hongwei Sun wrote: > Andrew, > > After investigation , we have the following responses to your > questions. > > (1) For NtVersion field in NETLOGON_SAM_LOGON_RESPONSE_EX or > NETLOGON_SAM_LOGON_RESPONSE, The returned value always has > NETLOGON_NT_VERSION_1 bit turned on , in addition to the original > request. > > For example, if 04:00:00:00 (NETLOGON_NT_VERSION_5EX) is sent as > request, NETLOGON_SAM_LOGON_RESPONSE response will be returned with > NtVersion equal to 05 (NETLOGON_NT_VERSION_5EX | > NETLOGON_NT_VERSION_1). For request > 08:00:00:00(NETLOGON_NT_VERSION_5EX_IP), the response will be 0D > ((NETLOGON_NT_VERSION_5EX | NETLOGON_NT_VERSION_5EX_IP| > NETLOGON_NT_VERSION_1). We will update the documentation in the > future release. > > (2) lmNTToken and NT20Token should be 0xFFFF. We will incorporate > the changes to the documentation.
Thanks. Per my original question: > Are any of the expected values in this document backed by a testcase that > shows them to be true? Can you give any status on if this protocol has been though your testsuite building process yet? Thanks, -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
