summaryrefslogtreecommitdiffstats
path: root/source3
Commit message (Collapse)AuthorAgeFilesLines
* s3-spoolss: Fix _spoolss_EnumPrinters servername handling.Günther Deschner2010-02-181-1/+1
| | | | Guenther
* s3-selftest: fix return code for modprinter.pl -a.Günther Deschner2010-02-181-1/+2
| | | | | | | | | | | Background is: the SetPrinter level 2 calls "addprinter command" an fails if a share already existed (and the addprinter command returned a non-0 return code). Removing the non-0 return code is fine, as in AddPrinter{Ex}, we have checks to see if a share already exists before calling out the addprinter command. Maybe one day, we need to have a "changeprinter command"... Guenther
* s3-selftest: finally enable RPC-SPOOLSS-PRINTER against Samba 3.Günther Deschner2010-02-181-1/+2
| | | | Guenther
* s3-selftest: include addprinter/deleteprinter command.Günther Deschner2010-02-182-0/+131
| | | | Guenther
* s3-spoolss: fix return code of spoolss_DeletePrinter.Günther Deschner2010-02-181-1/+1
| | | | | | | | When the printer has been removed by the "deleteprinter command", we need to check if it is still there and then fail, not fail if we successfully removed it (found by RPC-SPOOLSS-PRINTER). Guenther
* s3-spoolss: in spoolss_EnumPrinters r->in.server is a *unique* pointer!Günther Deschner2010-02-181-3/+5
| | | | Guenther
* s3-spoolss: more AddPrinter{Ex} checks.Günther Deschner2010-02-181-0/+18
| | | | | | | | | Windows will allow to add a non-shared printer that is returned by EnumPrinters. Samba has no notion of non-shared local printers yet, so just make sure to behave like we do elsewhere: a printer autoloaded by samba or added to samba is shared. Guenther
* s3-spoolss: add some printer info validation for AddPrinter calls.Günther Deschner2010-02-181-0/+22
| | | | Guenther
* s3-modules: fix get_acl_blob in the acl_tdb VFS module.Günther Deschner2010-02-181-1/+1
| | | | | | Shuttle-reviewed by jra :) Guenther
* s3-rpcclient: fix uninitialized variable in wkssvc_enumerateusers.Günther Deschner2010-02-181-2/+2
| | | | Guenther
* Fix bug #7146 - Samba miss-parses authenticated RPC packets.Jeremy Allison2010-02-174-138/+363
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Parts of the Samba RPC client and server code misinterpret authenticated packets. DCE authenticated packets actually look like this : +--------------------------+ |header | | ... frag_len (packet len)| | ... auth_len | +--------------------------+ | | | Data payload | ... .... | | +--------------------------+ | | | auth_pad_len bytes | +--------------------------+ | | | Auth footer | | auth_pad_len value | +--------------------------+ | | | Auth payload | | (auth_len bytes long) | +--------------------------+ That's right. The pad bytes come *before* the footer specifying how many pad bytes there are. In order to read this you must seek to the end of the packet and subtract the auth_len (in the packet header) and the auth footer length (a known value). The client and server code gets this right (mostly) in 3.0.x -> 3.4.x so long as the pad alignment is on an 8 byte boundary (there are some special cases in the code for this). Tridge discovered there are some (DRS replication) cases where on 64-bit machines where the pad alignment is on a 16-byte boundary. This breaks the existing S3 hand-optimized rpc code. This patch removes all the special cases in client and server code, and allows the pad alignment for generated packets to be specified by changing a constant in include/local.h (this doesn't affect received packets, the new code always handles them correctly whatever pad alignment is used). This patch also works correctly with rpcclient using sign+seal from the 3.4.x and 3.3.x builds (testing with 3.0.x and 3.2.x to follow) so even as a server it should still work with older libsmbclient and winbindd code. Jeremy
* Fix bug #6557 - Do not work VFS full_auditJeremy Allison2010-02-171-51/+34
| | | | | | | | | | | Re-arrange the operations order so SMB_VFS_CONNECT is done first as root (to allow modules to correctly initialize themselves). Reviewed modules to check if they needed CONNECT invoked as a user (which we previously did) and it turns out any of them that cared needed root permissions anyway. Jeremy.
* s3: go straight to winbindd_dual_pam_auth() in case of !NT_STATUS_OKLars Müller2010-02-171-1/+1
| | | | | | At the formerly used process_result statement we have alone one NT_STATUS_IS_OK() which never could be hit in our case as we only go here if NT_STATUS_EQUAL is not ok.
* s3: let the pam_winbind po files reference the correct locationLars Müller2010-02-1720-644/+644
|
* s3: Fix bug 7139Volker Lendecke2010-02-171-2/+32
| | | | | To provide the user with the same SID when doing Kerberos logins, attempt to do a make_server_info_sam instead of a make_server_info_pw.
* s3:rpc streamline memory handlingSimo Sorce2010-02-161-13/+5
|
* s3: Fix timeout calculation if g_lock_lock is given a timeout < 60sVolker Lendecke2010-02-161-1/+6
| | | | Detected while showing this code to obnox :-)
* s3: Slightly increase parallelism in g_lockVolker Lendecke2010-02-161-1/+7
| | | | | There's no need to still hold the g_lock tdb-level lock while telling the waiters to retry
* s3: Avoid starving locks when many processes die at the same timeVolker Lendecke2010-02-161-6/+4
| | | | | | | In g_lock_unlock we have a little race between the process_exists and messaging_send call: We only send to 5 waiters now, they all might have died between us checking their existence and sending the message. This change makes g_lock_lock retry at least once every minute.
* s3: Avoid a thundering herd in g_lock_unlockVolker Lendecke2010-02-161-1/+16
| | | | | | Only notify the first 5 pending lock waiters. This avoids a thundering herd problem that is really nasty in a cluster. It also makes acquiring a lock a bit more FIFO, lock waiters are added to the end of the array.
* s3: Optimize g_lock_lock for a heavily contended caseVolker Lendecke2010-02-161-3/+36
| | | | | | Only check the existence of the lock owner in g_lock_parse, check the rest of the records only when we got the lock successfully. This reduces the load on process_exists which can involve a network roundtrip in the clustered case.
* s3: Fix handling of processes that died in g_lockVolker Lendecke2010-02-161-3/+5
| | | | | g_lock_parse might have thrown away entries from the locks array because the processes were not around anymore. Don't store the orphaned entries.
* s3: Fix a typoVolker Lendecke2010-02-151-1/+1
|
* spoolss: disable GetPrinterDriver level 101 (as called by XP).Günther Deschner2010-02-151-2/+6
| | | | | | | We still dont get the marshalling right, disable and XP will just fall back to level 6. Guenther
* s3: eventlogadm.c: add -s option to use alternative config file.Holger Hetterich2010-02-151-4/+15
| | | | Update the manpage accordingly.
* s3: Fix initgroups return checkPeter Watkins2010-02-141-1/+1
| | | | | A return code of 1 from initgroups() is OK since apparently it means the gid has already been set. The man page doesn't mention this.
* s3: last part of TYPESAFE_QSORT() conversionAndrew Tridgell2010-02-143-6/+5
| | | | convert smbcacls, sharesec and web/
* s3-smbd: convert lanman and notify code to TYPESAFE_QSORT()Andrew Tridgell2010-02-142-12/+4
|
* s3-rpc: convert wkssvc to use TYPESAFE_QSORT()Andrew Tridgell2010-02-141-10/+4
|
* s3-locking: convert brlock to TYPESAFE_QSORT()Andrew Tridgell2010-02-141-3/+2
|
* s3: convert registry and printing code to TYPESAFE_QSORT()Andrew Tridgell2010-02-143-8/+6
|
* s3-nmbd: note TODO item for qsortAndrew Tridgell2010-02-141-0/+2
| | | | This uses another char* cast hack. Left alone for now.
* s3-vfs: use TYPESAFE_QSORT() in s3 VFS modulesAndrew Tridgell2010-02-142-8/+6
|
* s3-lib: use TYPESAFE_QSORT() in remaining s3 library codeAndrew Tridgell2010-02-143-3/+6
| | | | | the sort_query_replies() in nmblib.c is a TODO. It uses a hack that treats a char* as a structure. I've left that one alone for now.
* s3-libsmb: use TYPESAFE_QSORT() in namequery codeAndrew Tridgell2010-02-141-14/+12
| | | | | This one was a bit trickier. I'd appreciate it if someone else can look over this.
* s3-lib: use TYPESAFE_QSORT() in s3 interfaces codeAndrew Tridgell2010-02-141-1/+1
|
* s3-includes: enable TYPESAFE_QSORT() in s3Andrew Tridgell2010-02-141-0/+1
|
* s3: Fix Coverity ID 629: DEADCODEVolker Lendecke2010-02-131-3/+0
| | | | We have already returned if (argc < 1) above
* s3: Fix bug 5198 -- parse chfn(1)-change gecos fieldVolker Lendecke2010-02-131-1/+34
|
* s3: Fix typo found by jhell <jhell@DataIX.net>Volker Lendecke2010-02-131-2/+2
|
* libwbclient: Separate out the async functionsKai Blin2010-02-131-5/+11
|
* s3: Remove unused comparison fn from "struct sorted_tree"Volker Lendecke2010-02-133-10/+4
|
* s3: Make adt_tree data definitions private to adt_tree.cVolker Lendecke2010-02-132-16/+15
|
* s3: SORTED_TREE -> struct sorted_treeVolker Lendecke2010-02-133-14/+16
|
* s3: TREE_NODE -> struct tree_nodeVolker Lendecke2010-02-132-17/+23
|
* s3: Fix some nonempty blank linesVolker Lendecke2010-02-131-69/+68
|
* s3: Fix a C++ warningVolker Lendecke2010-02-131-1/+1
|
* Use sec_initial_uid() in the places where being root doesn't matter,Jeremy Allison2010-02-125-5/+5
| | | | | | and 0 in the places where it does. Jeremy
* Simplify the logic in make_connection_snum(), and make it match Windows ↵Jeremy Allison2010-02-121-41/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | behavior. Cause all exit paths to go through one place, where all cleanup is done. change_to_root_user() for pathname operations that should succeed if the path exists, even if the connecting user has no access. For example, a share can now be defined with a path of /root/only/access (where /root/only/access is a directory path with all components only accessible to root e.g. root owned, permissions 700 on every component). Non-root users will now correctly connect, but get ACCESS_DENIED on all activities (which matches Windows behavior). Previously, non-root users would get NT_STATUS_BAD_NETWORK_NAME on doing a TConX to this share, even though it's a perfectly valid share path (just not accessible to them). This change was inspired by the research I did for bug #7126, which was reported by bepi@adria.it. As this is a change in a core function, I'm proposing to leave this only in master for 3.6.0, not back-port to any existing releases. This should give us enough time to decide if this is the way we want this to behave (as Windows) or if we prefer the previous behavior. Jeremy.
* Fix warning messages on compile in g_lock.c Volker & Michael please check.Jeremy Allison2010-02-121-14/+4
| | | | Jeremy.
generated by cgit (git 2.34.1) at 2025-09-26 23:12:45 +0000