| commit | f793c99ca54d62cb8142607e8449f5b5b3a5e79d | |
| author | Michael Adam <obnox@samba.org> | |
| Tue, 11 Dec 2007 12:05:44 +0000 (11 13:05 +0100) | ||
| committer | Michael Adam <obnox@samba.org> | |
| Thu, 13 Dec 2007 09:15:17 +0000 (13 10:15 +0100) | ||
| tree | f079aec566a4692d613b6fd27f3d8782f0a3d582 | treesnapshot (tar.gz zip) |
| parent | 5d9c97703432bbca7d45948708b5b21a3718559a | commitdiff |
Let get_trust_pw() determine the machine_account_name to use.
Up to now each caller used its own logic.
This eliminates code paths where there was a special treatment
of the following situation: the domain given is not our workgroup
(i.e. our own domain) and we are not a DC (i.e. it is not a typical
trusted domain situation). In situation the given domain name was
previously used as the machine account name, resulting in an account
name of DOMAIN\\DOMAIN$, which does not seem very reasonable to me.
get_trust_pw would not have obtained a password in this situation
anyways.
I hope I have not missed an important point here!
Michael
(This used to be commit 6ced4a7f88798dc449a667d63bc29bf6c569291f)
Up to now each caller used its own logic.
This eliminates code paths where there was a special treatment
of the following situation: the domain given is not our workgroup
(i.e. our own domain) and we are not a DC (i.e. it is not a typical
trusted domain situation). In situation the given domain name was
previously used as the machine account name, resulting in an account
name of DOMAIN\\DOMAIN$, which does not seem very reasonable to me.
get_trust_pw would not have obtained a password in this situation
anyways.
I hope I have not missed an important point here!
Michael
(This used to be commit 6ced4a7f88798dc449a667d63bc29bf6c569291f)
| source3/auth/auth_domain.c | diffblobblamehistory | |
| source3/passdb/passdb.c | diffblobblamehistory | |
| source3/rpc_client/cli_pipe.c | diffblobblamehistory | |
| source3/winbindd/winbindd_cm.c | diffblobblamehistory |