summaryrefslogtreecommitdiffstats
path: root/source3
Commit message (Collapse)AuthorAgeFilesLines
* s3-kerberos: support S4U2SELF impersionation through cli_krb5_get_ticket().Günther Deschner2009-11-062-6/+22
| | | | Guenther
* s3-kerberos: use smb_krb5_get_credentials in ads_krb5_mk_req.Günther Deschner2009-11-061-4/+7
| | | | Guenther
* s3-kerberos: modify cli_krb5_get_ticket to take a new impersonate_princ_s arg.Günther Deschner2009-11-065-8/+13
| | | | Guenther
* s3-net: better use memory credential cache in net_ads_kerberos_pac().Günther Deschner2009-11-061-1/+1
| | | | Guenther
* s3-net: allow to call "net ads kerberos pac <impersonation principal> -P".Günther Deschner2009-11-061-1/+7
| | | | Guenther
* s3-kerberos: add impersonate_principal for kerberos_return_pac_X calls.Günther Deschner2009-11-063-1/+28
| | | | Guenther
* s3-kerberos: add smb_krb5_get_tkt_from_creds().Günther Deschner2009-11-061-0/+40
| | | | Guenther
* s3-kerberos: fix some build warnings when building against heimdal.Günther Deschner2009-11-061-2/+2
| | | | Guenther
* s3-kerberos: add smb_krb5_get_{creds,credentials} incl. support for S4U2SELF ↵Günther Deschner2009-11-063-2/+284
| | | | | | impersonation. Guenther
* s3-kerberos: remove duplicate prototype.Günther Deschner2009-11-061-4/+0
| | | | Guenther
* s3-kerberos: add smb_krb5_parse_name_flags().Günther Deschner2009-11-062-1/+22
| | | | Guenther
* s3-kerberos: add configure checks for krb5_get_creds_X api.Günther Deschner2009-11-061-0/+3
| | | | Guenther
* Got the logic simplification worked out so we still passJeremy Allison2009-11-055-33/+50
| | | | | BASE-DELAYWRITE and also RAW-CLOSE. Jeremy.
* Revert commit "0551284dc08eb93ef7b2b2227a45e5ec21d482fb" - simplifyJeremy Allison2009-11-054-12/+34
| | | | | the logic. This was incorrect (I'll revisit this tomorrow). Jeremy.
* Remove the smbd:writetimeupdatedelay change Metze added. Metze pleaseJeremy Allison2009-11-052-3/+7
| | | | | | explain why you added this. Change --maximum-runtime=900 for smbtorture4 with BASE-DELAYWRITE. Should allow it to successfully complete now. Jeremy.
* Simplify the logic - remove extraneous argument and calls to ↵Jeremy Allison2009-11-054-34/+12
| | | | | | | | set_close_write_time(). We were treating a file time set on close as a sticky write time set, and I don't think it is. I will add a torture test later to RAW-CLOSE to confirm this. Jeremy.
* Fix explicit set of write time on close.Jeremy Allison2009-11-051-1/+5
| | | | Jeremy.
* Get closer to an accurate model of Windows timestamp changes.Jeremy Allison2009-11-056-32/+56
| | | | | | | | "Normal" non truncate writes always cause the timestamp to be set on close. Once a close is done on a handle this can reset the sticky write time to current time also. Updated smbtorture4 confirms this. Jeremy.
* s3: Fix a crash in notify_remove_onelevel when "change notify = no"Volker Lendecke2009-11-051-0/+4
|
* s3: Fix the talloc hierarchy in notify_remove_onelevelVolker Lendecke2009-11-051-1/+1
| | | | We want to free the record early, not when talloc_tos() is free'ed.
* s3: Add parameter "ctdb timeout"Volker Lendecke2009-11-055-5/+36
| | | | | | | | 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.
* s3: Fix kerberos refresh chain.Bo Yang2009-11-061-1/+3
| | | | Signed-off-by: Bo Yang <boyang@samba.org>
* Fix debug comment (brain wasn't working...).Jeremy Allison2009-11-041-2/+2
| | | | Jeremy.
* Filter the returned DOS attributes by 0xFF for clientsJeremy Allison2009-11-041-0/+12
| | | | | using older protocols (LANMAN2 or below). Jeremy.
* Remove "Protocol" as an extern, and add accessor functions.Jeremy Allison2009-11-049-30/+31
| | | | Jeremy.
* s3: add support for full windows timestamps resolution on filesBjörn Jacke2009-11-042-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.
* libcli/nbt Move more of lmhosts lookup into common codeAndrew Bartlett2009-11-041-45/+15
| | | | | | This aims to eventually share this with Samba4. Andrew Bartlett
* s3-netlogon: make sure we protect some function codes in ↵Günther Deschner2009-11-041-0/+13
| | | | | | _netr_LogonControl2Ex(). Guenther
* s3-netlogon: let s3 pass against RPC-NETLOGON-S3 again.Günther Deschner2009-11-041-0/+72
| | | | Guenther
* s3-netlogon: implement _netr_NETLOGON_INFO_4 in netr_LogonControl2Ex() and ↵Günther Deschner2009-11-041-0/+10
| | | | | | friends as well. Guenther
* s3-netlogon: implement remote trust account changing in ↵Günther Deschner2009-11-041-0/+41
| | | | | | netr_LogonControl2Ex() and friends. Guenther
* s3-lsa: fill in some more info levels in _lsa_QueryInfoPolicy().Günther Deschner2009-11-031-0/+32
| | | | | | Add dummys (just like s4 does) and fill in some more appropriate error codes. Guenther
* s3-passdb: cleanup some callers of pdb_get_trusteddom_pw().Günther Deschner2009-11-032-6/+2
| | | | Guenther
* Fix debug statements to use correct function name.Jeremy Allison2009-11-031-13/+13
| | | | Jeremy.
* requires_resume_key is a bool not int.Jeremy Allison2009-11-031-7/+2
| | | | Jeremy.
* Fix more of the RAW-SEARCH test. Older info levels areJeremy Allison2009-11-031-2/+9
| | | | | not 4 byte aligned (levels 1 - 3). Jeremy.
* s3: Remove debug_ctx()Volker Lendecke2009-11-0313-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.
* Convert from numbers to correct SMB_FIND_XX constant names.Jeremy Allison2009-11-021-8/+12
| | | | Jeremy.
* s3:registry: add an extra check for dsize==0 to regdb_fetch_keys_internal()Michael Adam2009-11-031-1/+1
| | | | | | | Don't only rely on dptr == NULL. I stumbled over this one when rewriting some of the dbwrap_ctdb code. Michael
* s3:registry: add safety check for return value of tdb_unpack to ↵Michael Adam2009-11-031-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
* s3:dbwrap_ctdb: add debug message to transaction_fetch_start()Michael Adam2009-11-031-0/+4
| | | | | | | | for the case that another local process has started a transaction bewteen releasing the transaction_lock record and starting the transaction. Michael
* s3:dbwrap_ctdb: split combined check in two and add descriptive debugMichael Adam2009-11-031-1/+14
| | | | | | | in db_ctdb_transaction_fetch_start() for error conditions when re-fetching the transaction_lock record inside the transaction Michael
* s3:dbwrap_ctdb: fix race condition with concurrent transactions on the same ↵Michael Adam2009-11-031-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
* s3:configure: add a check for the new CTDB_CONTROL_TRANS2_ACTIVEMichael Adam2009-11-031-0/+17
| | | | Michael
* s3:dbwrap_ctdb: add new db_ctdb_transaction_active() that calls ↵Michael Adam2009-11-031-0/+21
| | | | | | CTDB_CONTROL_TRANS2_COMMIT Michael
* s3:dbwrap_ctdb: fix a race in starting concurrent transactions on a single nodeMichael Adam2009-11-031-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
* s3:dbwrap_ctdb: use db_ctdb_ltdb_fetch() inside db_ctdb_transaction_fetch_startMichael Adam2009-11-031-6/+4
| | | | Michael
* s3:dbwrap_ctdb: use db_ctdb_ltdb_fetch() inside db_ctdb_transaction_fetch()Michael Adam2009-11-031-16/+6
| | | | Michael
* s3:dbwrap_ctdb: add a function db_ctdb_ltdb_fetch()Michael Adam2009-11-031-0/+53
| | | | | | This fetches a record from the db and splits out the ctdb header. Michael
* s3:dbrwap_ctdb: add a function db_ctdb_ltdb_store()Michael Adam2009-11-031-27/+39
| | | | | | and use it in db_ctdb_store() and db_ctdb_transaction_store(). Michael
generated by cgit (git 2.34.1) at 2024-10-14 05:23:46 +0000