[PATCH] DNS and Subdomain patches
Stefan (metze) Metzmacher
metze at samba.org
Fri Sep 5 01:08:46 MDT 2014
>>> Also, can you look at the subdomain-wip branch, not as a final review,
>>> but to let me know if I am working in the right direction? Do you have
>>> any comments on the approach taken in the patch? Is the idea to use smb
>>> signing in winbindd reasonable?
>> I think instead of using the machine account for smb authentication
>> against domain controllers of another domain, we should try to use
>> ncacn_ip_tcp, as windows does for netlogon connections.
>> Falling back to anonymous smb connections for ncacn_np.
>> The security of the DCERPC layer is enough for NETLOGON and LSA
>> when we use schannel for both.
>> I think we should try to use NetrEnumerateTrustedDomains()
>> in msrpc_trusted_domains() and only fallback (For older Samba DCs) to
>> lsa_EnumTrustDom*() as this seems to be the only thing that requires
>> cm_connect_lsa() and a policy handle, which is not available over
> I just looked, and this is what we already do in winbindd_ads.c. So we
> would only use LSA if we are not in security=ads mode, or we are talking
> to our internal domain.
>> For SAMR we can just use the machine account and SPNEGO with sign or seal
>> at the DCERPC layer, with a fallback to schannel.
>> At the DCERPC layer we should do a fallback to anonymous
>> only if we have winbind sealed pipes = no and require strong key = no.
>> If we use our machine account for smb against our own domain
>> we should force smb signing by default.
>> Is the domain trust account able to do smb authentication via krb5?
>> We should also think about changing the "client ldap sasl wrapping" default.
> I've added a patch for that.
>> What we also need is some more information in the list of domains.
>> We need to have a list of direct trusts (maybe with a priority)
>> and a list of all trusts, where each domain has a reference to the direct
>> trust that injected the domain. This is important
>> as we need to contact a dc of the direct trust when authenticating users
>> of indirect trusts. Currently we just use the IS_DC variable, and I
>> guess we do
>> the wrong thing if this is set to 'true'.
> This is the biggest task here, I've not started on this yet. We will
> require fully connected trusts for the timebeing.
Sounds ok for now.
>> Except for SAMR (which we should avoid as much as we can) we should only
>> ever contact
>> directly trusted domains and allow the remote dc forward netlogon and
>> lsa requests.
> I agree. SAMR should mainly be used for password changes.
The main user would be a trust against a Samba3 domain with security=domain.
wbinfo -u and wbinfo -g.
The thing we need to avoid for security=ads is LDAP. It has the same
Problems as SAMR.
In the long run I'd try to use the users credentials for "management"
which trigger SAMR or LDAP operations, e.g. via wbinfo commands.
Everything else should just use NETLOGON and LSA with schannel.
>> In addition to NETLOGON and LSA we could have a drsuapi connection
>> (using krb5)
>> for our own domain and other direct trusts.
>> Windows seems to forward LSA Lookup calls as DsCrackNames calls
>> (maybe only to GC servers).
> Thanks for the above. It wasn't as much trouble as I expected. I'll
> tidy up these patches and propose them.
Can you push them to the subdomain-wip branch for now?
> Any thoughts on other things like should we drop the GUID check on the AddRefs calls?
That look good.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: OpenPGP digital signature
More information about the samba-technical