search for: machine_account_secret

...Please let me know how. ./source3/wscript: conf.CHECK_FUNCS_IN('DES_pcbc_encrypt', 'crypto') As we already seem to check for libcrypto and store the dependency, you should be able to just add crypto to your list of deps. > no talloc stackframe at > ../../source3/passdb/machine_account_secrets.c:60, leaking memory > > So here's my second question: How do I avoid this warning? I guess you're missing a TALLOC_CTX *frame = talloc_stackframe(); in your initialisation. -slow -- Ralph Boehme, Samba Team https://samba.org/ SerNet Samba Team Lead https://serne...

.../source3/wscript:??? conf.CHECK_FUNCS_IN('DES_pcbc_encrypt', 'crypto') > > As we already seem to check for libcrypto and store the dependency, > you should be able to just add crypto to your list of deps. > >> no talloc stackframe at >> ../../source3/passdb/machine_account_secrets.c:60, leaking memory >> >> So here's my second question: How do I avoid this warning? > > I guess you're missing a > > TALLOC_CTX *frame = talloc_stackframe(); > > in your initialisation. > > -slow > > -- > Ralph Boehme, Samba Team???????? http...

...office.example.com] [S-1-5-21-3876585788-2465688680-3807591480] [2020/02/13 01:18:42.759997, 5] ../../source3/passdb/passdb.c:2396(get_trust_pw_clear2) get_trust_pw_clear2: could not fetch clear text trust account password for domain OFFICE [2020/02/13 01:18:42.760013, 5] ../../source3/passdb/machine_account_secrets.c:343(secrets_fetch_trust_account_password _legacy) secrets_fetch failed! [2020/02/13 01:18:42.760024, 5] ../../source3/passdb/passdb.c:2475(get_trust_pw_hash2) get_trust_pw_hash: could not fetch trust account password for domain OFFICE [2020/02/13 01:18:42.760896, 3] ../../lib/ldb-samba/ldb...

...Windows DNS (this is not a legacy NT4 style domain). So, this search fails also and the whole JOIN then fails. So the question is: Why isn't "SECRETS/$MACHINE.ACC/OFFICE" found in secrets.tdb? Grepping the samba source code only shows two places where this key is referenced: files: machine_account_secrets.c and samba3/_init_.py. Both uses are READ accesses. So, who WRITES this key - somewhere in the code, I would think. Or, does it come from the Windows side during the join and replication? Here's the relevant log entries in log.winbindd... [2020/02/14 16:59:37.564101, 3] ../../source3/win...

...initialize_password_db(False, NULL); get_global_sam_sid(); domain=lp_workgroup(); After this initialization the daemon accepts connections and calls local_change_password() Works very well but initialize_password_db() produces the following warning: no talloc stackframe at ../../source3/passdb/machine_account_secrets.c:60, leaking memory So here's my second question: How do I avoid this warning? Peter

...47.209422, 5] rpc_client/cli_pipe.c:1521(check_bind_response) check_bind_response: accepted! [2012/09/04 15:51:47.209687, 5] passdb/passdb.c:2365(get_trust_pw_clear) get_trust_pw_clear: could not fetch clear text trust account password for domain XXXXXX [2012/09/04 15:51:47.209844, 5] passdb/machine_account_secrets.c:267(secrets_fetch_trust_account_password_legacy) secrets_fetch failed! [2012/09/04 15:51:47.209998, 5] passdb/passdb.c:2403(get_trust_pw_hash) get_trust_pw_hash: could not fetch trust account password for domain XXXXXXX [2012/09/04 15:51:47.210109, 0] rpc_client/cli_pipe_schannel.c:54(get_...

...smberr.c Compiling ../libcli/util/doserr.c Compiling libsmb/errormap.c Compiling ../librpc/rpc/dcerpc_error.c Compiling ../libcli/auth/smbdes.c Compiling ../libcli/auth/smbencrypt.c Compiling ../libcli/auth/msrpc_parse.c Compiling ../libcli/auth/session.c Compiling passdb/secrets.c Compiling passdb/machine_account_secrets.c Compiling passdb/machine_sid.c Compiling librpc/gen_ndr/ndr_secrets.c Compiling libsmb/unexpected.c Compiling libsmb/namecache.c Compiling libsmb/nmblib.c Compiling libsmb/namequery.c Compiling ../libcli/nbt/lmhosts.c Compiling libsmb/conncache.c Compiling libads/dns.c Compiling libads/sitename_...