summaryrefslogtreecommitdiffstats
path: root/source3
Commit message (Collapse)AuthorAgeFilesLines
...
* s3:build: improve the check for a working krb5-config.Michael Adam2009-02-171-1/+1
| | | | | | | | | | | Not only check if it exists and is executable, but also check whether it accepts the command line "krb5-config --libs gssapi". Chris Hoogendyk <hoogendyk@bio.umass.edu> has reported configure failing on a Solaris machine due to krb5-config raising errors on these options. Michael
* s3-spoolss: remove old spoolss_ResetPrinter.Günther Deschner2009-02-173-62/+0
| | | | Guenther
* s3-spoolss: use pidl for _spoolss_ResetPrinter.Günther Deschner2009-02-172-38/+10
| | | | Guenther
* s3-netapi: fix Coverity #881 and #882.Günther Deschner2009-02-171-7/+56
| | | | Guenther
* Fix an invalid typecastingVolker Lendecke2009-02-171-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | entry->num_of_strings is a uint16_t. Casting it with (int *)&entry->num_of_strings is wrong, because it gives add_string_to_array the illusion that the object "num" points to is an int, which it is not. In case we are running on a machine where "int" is 32 or 64 bits long, what happens with that cast? "add_string_to_array" interprets the byte field that starts where "num_of_strings" starts as an int. Under very particular circumstances this might work in a limited number of cases: When the byte order of an int is such that the lower order bits of the int are stored first, the subsequent bytes which do not belong to the uint16_t anymore happen to be 0 and the result of the increment still fits into the first 2 bytes of that int, i.e. the result is < 65536. The correct solution to this problem is to use the implicit type conversion that happens when an assignment is done. BTW, this bug is found if you compile with -O3 -Wall, it shows up as a warning: rpc_server/srv_eventlog_lib.c:574: warning: dereferencing type-punned pointer will break strict-aliasing rules Thanks, Volker
* s3-rpcclient: use rpccli_spoolss_RemoteFindFirstPrinterChangeNotifyEx.Günther Deschner2009-02-171-20/+29
| | | | Guenther
* Fix bug 5920Yasuma Takeda2009-02-161-1/+1
| | | | | The length of the memcpy was calculated wrong, r->out.return_authenticator is a pointer
* s3:netlogon: implement _netr_LogonGetCapabilities() with ↵Stefan Metzmacher2009-02-161-4/+3
| | | | | | | | NT_STATUS_NOT_IMPLEMENTED This hopefully fixes bug #6100. metze
* s3 auth: Add parameter that forces every user through an NSS lookupZach Loafman2009-02-163-4/+35
| | | | | | When set to yes, "force username map" forces every user, even AD users, through an NSS lookup. This allows the token to be overridden with information from NSS in certain broken environments.
* s3 perfcount: Fix segfault with smbclient 'echo 3 foo'Tim Prouty2009-02-161-33/+11
|
* s3 OneFS: Add defaults to the fake timestamp parametersTim Prouty2009-02-162-8/+19
|
* make receive_smb_raw_talloc more readableTim Prouty2009-02-161-4/+4
|
* Attempt to fix bug #6099. According to MicrosoftJeremy Allison2009-02-151-17/+26
| | | | | | | | | | Windows 7 looks at the negotiate_flags returned in this structure *even if the call fails with access denied ! So in order to allow Win7 to connect to a Samba NT style PDC we set the flags before we know if it's an error or not. Jeremy.
* remove accidental white spaceDerrell Lipman2009-02-141-1/+0
|
* enums are traditionally signed. Avoid use of high bit in bit flags.Derrell Lipman2009-02-141-3/+3
|
* Get rid of the warnings I had for testingDerrell Lipman2009-02-141-5/+0
|
* It seems some systems use f_flags instead of f_flag. Use the appropriate one.Derrell Lipman2009-02-142-4/+28
|
* Remove a pointless NULL checkVolker Lendecke2009-02-141-3/+0
|
* Fix some nonempty blank linesVolker Lendecke2009-02-141-22/+22
|
* Rename lp_smb_perfcount_module() to lp_perfcount_module() to match the ↵Volker Lendecke2009-02-143-3/+3
| | | | parameter name
* Replace a // style comment with a /* */ oneVolker Lendecke2009-02-141-1/+1
|
* Fix some C++ warningsVolker Lendecke2009-02-141-7/+14
|
* Make smb_load_perfcount_module staticVolker Lendecke2009-02-141-1/+1
|
* f_frsize field is not ubiquitous. Check for it.Derrell Lipman2009-02-141-0/+4
|
* The f_fsid field is not always an integer type. Don't set it in that case.Derrell Lipman2009-02-141-0/+5
|
* Ensure consistency of values on stack (caught by AIX compiler)Derrell Lipman2009-02-141-16/+16
|
* Check for the right error return valueDerrell Lipman2009-02-141-2/+3
|
* [Bug 6069] Add a fstatvfs function for libsmbclientDerrell Lipman2009-02-144-26/+11
| | | | | | | - Revert Tim's changes for the moment. I need to see what the issue is and arrange to use "struct statvfs" if at all possible. Derrell
* Attempt to fix the build on Solaris 8Volker Lendecke2009-02-141-1/+1
|
* Fix a valgrind errorVolker Lendecke2009-02-141-1/+5
|
* s3 OneFS: Add recvfile implementationTim Prouty2009-02-133-0/+198
|
* s3 vfs: Fix SMB_VFS_RECVFILE/SENDFILE macrosTim Prouty2009-02-131-4/+4
|
* s3: Fix uninitialized const char *Tim Prouty2009-02-131-0/+1
|
* Enable total anonymization in vfs_smb_traffic_analyzer, by mapping any user ↵Holger Hetterich2009-02-131-5/+16
| | | | names to the one given by anonymize_prefix, without generating a hash number. This setting is optional and is compatible with the module configuration format of Samba 3.3.
* s3-spoolss: remove unused convert_printer_info.Günther Deschner2009-02-141-31/+0
| | | | Guenther
* s3-spoolss: use pidl for _spoolss_SetPrinter.Günther Deschner2009-02-143-61/+31
| | | | Guenther
* s3-spoolss: use pidl for _spoolss_AddPrinterEx.Günther Deschner2009-02-143-64/+31
| | | | Guenther
* s3-spoolss: add printer_info2_to_nt_printer_info2 and convert_printer_info_new.Günther Deschner2009-02-141-0/+67
| | | | Guenther
* s3-rpcclient: use rpccli_spoolss_AddPrinterEx.Günther Deschner2009-02-141-16/+42
| | | | Guenther
* s3-netlogon: some more appropriate debug messages.Günther Deschner2009-02-141-13/+31
| | | | Guenther
* Merge branch 'master' of ssh://jra@git.samba.org/data/git/sambaJeremy Allison2009-02-132-3/+1
|\
| * s3: Fix uninitialized variable warning (and bug).Zack Kirsch2009-02-132-3/+1
| |
* | Parameterize in local.h the MAX_RPC_DATA_SIZE, and ensureJeremy Allison2009-02-133-1/+56
|/ | | | | | that "offered" read from the rpc packet in spoolss is under that size. Tidyup from analysis from Veracode. Jeremy.
* Noted by Vericode analysis. Correctly use chroot().Jeremy Allison2009-02-131-1/+5
| | | | Jeremy.
* s3 libsmbclient: Fix fstatvfs to be more portableTim Prouty2009-02-134-11/+26
| | | | | | | | | | | The statvfs struct isn't guaranteed to be portable across operating systems. Since libsmbclient isn't actually calling statvfs and just using the statvfs struct to store similar information, this patch adds a new portable smbc_statvfs struct. This fixes a few of the failures in the build farm introduced by: ae259575c447e61665c8e7070c476914161b953f Derrell, please check.
* s3 OneFS: Add vfs implementation for SMB_VFS_GET_REAL_FILE_NAMEAravind Srinivasan2009-02-131-0/+41
|
* s3: Test module for perfcount systemtodd stecher2009-02-133-1/+370
| | | | | Add 'perfcount module = pc_test' to exercise this module. Results are logged into smb.log every 50 operations (configurable via smb.conf).
* Fix Coverity ID 740 (RESOURCE_LEAK)Volker Lendecke2009-02-131-0/+2
|
* Fix the build. When you do "make distclean; ./autogen; ./configure; make" ↵Jeremy Allison2009-02-131-0/+2
| | | | | | and it still doesn't build you know it's messed up. Jeremy.
* OneFS implementation of BRL VFS ops:Zack Kirsch2009-02-135-4/+479
| | | | | | | | | | | | | | | | | | | | | | | | | * Much of the beginning should look familiar, as I re-used the OneFS oplock callback record concept. This was necessary to keep our own state around - it really only consists of a lock state, per asynchronous lock that is currently unsatisfied. The onefs_cbrl_callback_records map to BLRs by the id. * There are 4 states an async lock can be in. NONE means there is no async currently out for the lock, as opposed to ASYNC. DONE means we've locked *every* lock (keep in mind a request can ask for multiple locks at a time.) ERROR is an error. * onefs_cbrl_async_success: The lock_num is incremented, and the state changed, so that when process_blocking_lock_queue is run, we will try the *next* lock, rather than the same one again. * onefs_brl_lock_windows() has some complicated logic: * We do a no-op if we're passed a BLR and the matching state is ASYNC -- this means Samba is trying to get the same lock twice, and we just need to wait longer, so we return an error. * PENDING lock calls happen when the lock is being queued on the BLQ -- we do async in this case. * We also do async in the case that we're passed a BLR, but the lock is not pending. This is an async lock being probed by process_blocking_lock_queue. * We do a sync lock for any normal first request of a lock. * Failure is returned, but it doesn't go to the client unless the lock has actually timed out.
generated by cgit (git 2.34.1) at 2025-09-29 08:26:26 +0000