summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2009-11-05s4:dcesrv_samr - Implement "dcesrv_samr_ValidatePassword" using my new check ↵Matthias Dieter Wallnöfer1-7/+49
password call This implements a very basic method for password validation using my new "samdb_check_password" call.
2009-11-05s4:dsdb/common/util - Add a new utility function "samdb_check_password"Matthias Dieter Wallnöfer1-9/+45
This function performs basic password checks and will be used by the "samrValidatePassword" call and the "password_hash" module.
2009-11-05s4:samdb_set_password/samdb_set_password_sid - Better comments and cosmeticsMatthias Dieter Wallnöfer1-28/+34
2009-11-05s3: Add parameter "ctdb timeout"Volker Lendecke6-5/+73
When something in the cluster blocks, it can happen that we wait indefinitely long for ctdb, just adding to the blocking condition. In theory, nothing should block, but as someone said "In practice the difference between theory and practice is larger than in theory". This adds a timeout parameter in seconds, after which we stop waiting for ctdb and panic.
2009-11-05s4:samdb python bindings - add a wrapper for "dsdb_make_schema_global"Matthias Dieter Wallnöfer1-0/+17
2009-11-05s4:samdb python bindings - make the python wrap connect more like the C oneMatthias Dieter Wallnöfer1-3/+10
Add call for setting the create permissions.
2009-11-05s4:samdb python bindings - Reorder some function bodies to match the order ↵Matthias Dieter Wallnöfer1-25/+24
in "ldb_wrap_connect"
2009-11-05s4:kdc: remove unused struct kpasswd_socketStefan Metzmacher1-10/+0
metze
2009-11-06s3: Fix kerberos refresh chain.Bo Yang1-1/+3
Signed-off-by: Bo Yang <boyang@samba.org>
2009-11-04Fix debug comment (brain wasn't working...).Jeremy Allison1-2/+2
Jeremy.
2009-11-04Filter the returned DOS attributes by 0xFF for clientsJeremy Allison1-0/+12
using older protocols (LANMAN2 or below). Jeremy.
2009-11-04Remove "Protocol" as an extern, and add accessor functions.Jeremy Allison9-30/+31
Jeremy.
2009-11-04s3: add support for full windows timestamps resolution on filesBjörn Jacke2-6/+14
setting nanosecond timestamps using utimensat() was first supported by Linux kernel 2.6.22 and glibc 2.6. It's specified in POSIX.1-2008. This effectively makes us use Windows' full 100ns timestamp resolution - actually just an improvement from 10^-6 to 10^-7. For now Linux CIFS vfs will also just be able to make use of 100ns resolution, not 1ns.
2009-11-04Added security descriptor for the domain NC to provisioning.Nadezhda Ivanova2-1/+61
Necessary for correct descriptor inheritance. Based on the default state of a single DC. Will be modified later when we support multiple DCs.
2009-11-04s4:provisioning - Fixed minor bugs in provisioning tool and partition module.Endi S. Dewata2-3/+4
2009-11-04libcli/nbt Move more of lmhosts lookup into common codeAndrew Bartlett3-45/+100
This aims to eventually share this with Samba4. Andrew Bartlett
2009-11-04lib/util Fix comments in rfc1738.c.Andrew Bartlett1-3/+3
The Samba version does not use static buffers Andrew Bartlett
2009-11-04s3-netlogon: make sure we protect some function codes in ↵Günther Deschner1-0/+13
_netr_LogonControl2Ex(). Guenther
2009-11-04s3-netlogon: let s3 pass against RPC-NETLOGON-S3 again.Günther Deschner1-0/+72
Guenther
2009-11-04s3-netlogon: implement _netr_NETLOGON_INFO_4 in netr_LogonControl2Ex() and ↵Günther Deschner1-0/+10
friends as well. Guenther
2009-11-04s3-netlogon: implement remote trust account changing in ↵Günther Deschner1-0/+41
netr_LogonControl2Ex() and friends. Guenther
2009-11-03security: re-run make samba3-idl after IDL change.Günther Deschner2-25/+0
Guenther
2009-11-03s3-lsa: fill in some more info levels in _lsa_QueryInfoPolicy().Günther Deschner1-0/+32
Add dummys (just like s4 does) and fill in some more appropriate error codes. Guenther
2009-11-03s4-smbtorture: skip three info levels while testing s3 with RPC-LSA.Günther Deschner1-3/+14
These are only supported by s3 when running pdb_ads atm. Guenther
2009-11-03s4-smbtorture: skip QueryInfoPolicy2 while running RPC-LSA against s3.Günther Deschner1-0/+4
This is only supported by s3 when running pdb_ads atm. Guenther
2009-11-03s4-smbtorture: skip QueryDomainInformationPolicy test against s3 in RPC-LSA.Günther Deschner1-0/+4
Guenther
2009-11-03s4-smbtorture: simplify some torture_comments in RPC-LSA.Günther Deschner1-20/+6
Guenther
2009-11-03s3-passdb: cleanup some callers of pdb_get_trusteddom_pw().Günther Deschner2-6/+2
Guenther
2009-11-03Fix debug statements to use correct function name.Jeremy Allison1-13/+13
Jeremy.
2009-11-03requires_resume_key is a bool not int.Jeremy Allison1-7/+2
Jeremy.
2009-11-03Fix more of the RAW-SEARCH test. Older info levels areJeremy Allison1-2/+9
not 4 byte aligned (levels 1 - 3). Jeremy.
2009-11-03tsocket: rewrite tsocket_guide.txt to reflect the current APIsStefan Metzmacher1-467/+413
metze
2009-11-03tsocket_bsd: return -1 and set errno to ENAMETOOLONG if the unix path is too ↵Stefan Metzmacher1-1/+6
long metze
2009-11-03tsocket: remove prototype of non-existing tsocket_address_inet_set_broadcast()Stefan Metzmacher1-2/+0
metze
2009-11-03Fixed some missing flags and bugs in the security creation.Nadezhda Ivanova1-11/+47
Also, added some logging. It needs improvement, possibly ability to turn in on and off via configuration file.
2009-11-03Fixed a bug in object specific access checks.Nadezhda Ivanova1-2/+4
2009-11-03s3: Remove debug_ctx()Volker Lendecke13-86/+70
smbd just crashed on me: In a debug message I called a routine preparing a string that itself used debug_ctx. The outer routine also used it after the inner routine had returned. It was still referencing the talloc context that the outer debug_ctx() had given us, which the inner DEBUG had already freed.
2009-11-03Added some dn to the info in the log messages.Nadezhda Ivanova1-3/+3
2009-11-03Removed the default DACL from token, as we will not be using it.Nadezhda Ivanova1-1/+0
2009-11-02Convert from numbers to correct SMB_FIND_XX constant names.Jeremy Allison1-8/+12
Jeremy.
2009-11-03s3:registry: add an extra check for dsize==0 to regdb_fetch_keys_internal()Michael Adam1-1/+1
Don't only rely on dptr == NULL. I stumbled over this one when rewriting some of the dbwrap_ctdb code. Michael
2009-11-03s3:registry: add safety check for return value of tdb_unpack to ↵Michael Adam1-0/+4
regdb_fetch_keys_internal() Prevents segfaults in some situations. (For a non existent or empty record, we sometimes rely on the fetch operation to return dsize==0 and sometimes we rely on dptr==NULL.) Michael
2009-11-03s3:dbwrap_ctdb: add debug message to transaction_fetch_start()Michael Adam1-0/+4
for the case that another local process has started a transaction bewteen releasing the transaction_lock record and starting the transaction. Michael
2009-11-03s3:dbwrap_ctdb: split combined check in two and add descriptive debugMichael Adam1-1/+14
in db_ctdb_transaction_fetch_start() for error conditions when re-fetching the transaction_lock record inside the transaction Michael
2009-11-03s3:dbwrap_ctdb: fix race condition with concurrent transactions on the same ↵Michael Adam1-0/+12
node. In ctdb_transaction_commit(), when the trans2_commit control fails, there is a race condition in the 1 second sleep between the local transaction_cancel and the call to ctdb_replay_transaction(): The database is not locked, and neither is the transaction_lock record. So another client can start and possibly complete a new transaction in this gap, but only on the same node: The locking of the transaction_lock record on a different node which involves migration of the record to the other node has been disabled by introduction of the transaction_active flag on the db which closes precisely this gap from the start of the commit until the call to TRANS2_FINISH or TRANS2_ERROR. But this mechanism does not cover the case where a process on the same node tries to start a transaction: There is no obstacle to locking the transaction_lock record because the record does not need to be migrated. This commit closes this race condition in ctdb_transaction_fetch_start() by using the new ctdb_ctrl_transaction_active() call to ask the local ctdb daemon whether it has a transaction running on the database. If so, the check is repeated until the running transaction is done. This does introduce an additional call to the local ctdbd when starting transactions, but it does close the (hopefully) last race condition. Michael
2009-11-03s3:configure: add a check for the new CTDB_CONTROL_TRANS2_ACTIVEMichael Adam1-0/+17
Michael
2009-11-03s3:dbwrap_ctdb: add new db_ctdb_transaction_active() that calls ↵Michael Adam1-0/+21
CTDB_CONTROL_TRANS2_COMMIT Michael
2009-11-03s3:dbwrap_ctdb: fix a race in starting concurrent transactions on a single nodeMichael Adam1-0/+25
There are two races in concurrent transactions on a single node. One in starting a transaction and one with replay during commit. This commit closes the first race by storing the client pid in the transaction-lock record and comparing the stored pid against its own pid after releasing the lock and refetching the record inside the transaction. Michael
2009-11-03s3:dbwrap_ctdb: use db_ctdb_ltdb_fetch() inside db_ctdb_transaction_fetch_startMichael Adam1-6/+4
Michael
2009-11-03s3:dbwrap_ctdb: use db_ctdb_ltdb_fetch() inside db_ctdb_transaction_fetch()Michael Adam1-16/+6
Michael
generated by cgit (git 2.34.1) at 2024-07-15 14:31:47 +0000