summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* s4:setup Add DisplaySpecifiers from Microsoft.Andrew Bartlett2009-09-075-0/+148158
| | | | | | | | Like the schema, these are provided under the licence at the head of the file, which is not the GPL, but allows us to distribute them with Samba. Andrew Bartlett
* s4: bring nsupdate-gss into the s4 treeAndrew Tridgell2009-09-072-0/+379
| | | | | | | | This is a perl script that does TSIG-GSS DNS updates against a AD DC. The bind 9.5 nsupdate still doesn't seem to work with TSIG-GSS, and we need a way to do DNS updates when we vampire a domain, so I revived this ancient perl script and added a wrapper script that can update DNS entries using our machine account credentials
* s4: fixed the secrets.ldb construction in libnetAndrew Tridgell2009-09-071-8/+8
| | | | | on a vampire join we were not putting the right attributes and objectclass on the secrets.ldb record
* s4: the secrets.ldb module needs the loadparm opaque setupAndrew Tridgell2009-09-071-0/+7
|
* s3:winbind: Convert WINBINDD_SET_HWM to the new APIVolker Lendecke2009-09-0715-128/+454
|
* s3:winbind: Convert WINBINDD_REMOVE_MAPPING to the new APIVolker Lendecke2009-09-0715-108/+488
|
* s3:winbind: Convert WINBINDD_SET_MAPPING to the new APIVolker Lendecke2009-09-0715-106/+538
|
* s3:winbind: Convert WINBINDD_CHECK_MACHACC to the new APIVolker Lendecke2009-09-0715-76/+451
|
* s3:smbd: Add the ntstatus to the smb_panic in share_mode_lock_destructorVolker Lendecke2009-09-071-2/+18
| | | | This might help finding why bug 6518 happens
* s4:simple_ldap_map - Enhance it for supporting "primaryGroupID" in the right wayMatthias Dieter Wallnöfer2009-09-061-14/+25
|
* s4:torture - Fix uninitialized variableMatthias Dieter Wallnöfer2009-09-061-1/+1
|
* s4:"linked attributes" modules - correct the commentsMatthias Dieter Wallnöfer2009-09-061-2/+2
|
* s4: Fix typoMatthias Dieter Wallnöfer2009-09-061-2/+2
|
* s4:pwsettings - Introduce the LDB modify flags in the right wayMatthias Dieter Wallnöfer2009-09-061-27/+8
| | | | | We can't emulate them through the LDB changetype flags since they haven't the same constants! The previous behaviour led to huge problems.
* s4:ldb_errors - add spacesMatthias Dieter Wallnöfer2009-09-061-0/+2
|
* s4:dsdb/common/util.c - Copy parameters to prevent segfaultsMatthias Dieter Wallnöfer2009-09-061-3/+8
| | | | | The parameters "lmNewHash" and/or "ntNewHash" could be NULL and when we perform write operations on them (look below in the code) we could get SIGSEGVs!
* s4:dsdb/common/util - Indentation fixesMatthias Dieter Wallnöfer2009-09-061-4/+5
|
* Tell newbie devs about ./configure.developerRusty Russell2009-09-062-2/+2
| | | | | | Enhances the outputs in autogen.sh for both s3 and s4. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
* Check we read off the compelte event from inotifySimo Sorce2009-09-051-2/+8
| | | | | | | The kernel may return a short read, so we must use read_data() to make sure we read off the full buffer. If somethign bad happens we also need to kill the inotify watch because the filedescriptor will return out of sync structures if we read only part of the data.
* Save and report the correct errno value.Simo Sorce2009-09-051-8/+12
|
* s3:winbind: Use fstr_sprintf, it is simpler than talloc_asprintf->fstrcpyVolker Lendecke2009-09-051-8/+5
|
* s3:winbind: Remove pointless <cond> ? true : false;Volker Lendecke2009-09-051-4/+4
|
* s3:winbind: Make the pam_auth subfunctions staticVolker Lendecke2009-09-052-18/+9
|
* s3:libsmb: Convert (state->received) to (state->received != 0)Volker Lendecke2009-09-051-1/+1
| | | | This confused me for a second, this should not happen a second time :-)
* util:tests: Correct time tests for negative UTC offsets.Andrew Kroeger2009-09-051-2/+23
| | | | | | | | | | | | | | | | | | | | | | | All: Please find attached a patch to fix the timestring and http_timestring tests on hosts that have a negative UTC offset (west of the Prime Meridian). Sincerely, Andrew Kroeger >From 8a8ca35edccf64aa98f2f3ae1469c4c27db8215e Mon Sep 17 00:00:00 2001 From: Andrew Kroeger <andrew@id10ts.net> Date: Fri, 4 Sep 2009 01:31:50 -0500 Subject: [PATCH] util:tests: Correct time tests for negative UTC offsets. The timestring and http_timestring tests were failing on hosts with negative offsets from UTC. Due to the timezone offset, the returned values were back in the year 1969 (before the epoch) and did not match the test patterns. The correction computes the offset from UTC, and if it is negative that offset is added onto the value given to the timestring() and http_timestring() calls so that the returned values fall on 01-Jan-1970 and match the test pattern.
* selftest: Account for 0-based months in date parsing and printing.Andrew Kroeger2009-09-051-3/+3
| | | | | | | | | | | | | | | | | All: Please find attached 2 patches to correct date/time parsing and output in the Subunit processing. The first patch corrects the logic to account for months being 0-based. The second corrects the time formatting, as it is dealing with local, not "Z"ulu (UTC) time. Sincerely, Andrew Kroeger >From 3cf81eea1309084a973359c7f6a2375d5d20a3f0 Mon Sep 17 00:00:00 2001 From: Andrew Kroeger <andrew@id10ts.net> Date: Fri, 4 Sep 2009 01:24:00 -0500 Subject: [PATCH] selftest: Account for 0-based months in date parsing and printing.
* Add release script for teventtevent-0.9.8Simo Sorce2009-09-041-0/+48
|
* s4:configure: require tevent >= 0.9.8Stefan Metzmacher2009-09-041-1/+1
| | | | metze
* tevent: change version to 0.9.8 after some critical bugs have been fixedStefan Metzmacher2009-09-041-1/+1
| | | | metze
* cifs.upcall: do a brute-force search for KRB5 credcacheJeff Layton2009-09-041-46/+138
| | | | | | | | | | | | | | | | | | | | A few weeks ago, I added some code to cifs.upcall to take the pid sent by the kernel and use that to get the value of the $KRB5CCNAME environment var for the process. That works fine on the initial mount, but could be problematic on reconnect. There's no guarantee on a reconnect that the process that initiates the upcall will have $KRB5CCNAME pointed at the correct credcache. Because of this, the current scheme isn't going to be reliable enough and we need to use something different. This patch replaces that scheme with one very similar to the one used by rpc.gssd in nfs-utils. It searches the credcache dir (currently hardcoded to /tmp) for a valid credcache for the given uid. If it finds one then it uses that as the credentials cache. If it finds more than one, it uses the one with the latest TGT expiration. Signed-off-by: Jeff Layton <jlayton@redhat.com>
* s4:python fixed subunit tests of dcerpcAndrew Tridgell2009-09-047-6/+6
| | | | | | The version of the unitest python module in Ubuntu Jaunty doesn't seem to support this many level of subdirectories. Moving the tests up one level solves the problem.
* ldb: make ldb module programming less error proneAndrew Tridgell2009-09-042-0/+17
| | | | | | | | | | | | | When a top level method in a module returns an error, it is supposed to call ldb_module_done(). We ran across a case where this wasn't done, and then found that in fact that are hundreds of similar cases in our modules. It took Andrew and I a full day to work out that this was the cause of a subtle segv in another part of the code. To try to prevent this happening again, this patch changes ldb_next_request() to catch the error by checking if a module returning an error has called ldb_module_done(). If it hasn't then the call is made on behalf of the module.
* s3:winbind: Fix Coverity ID 933: FORWARD_NULLVolker Lendecke2009-09-041-0/+1
|
* s3:smbd: Fix Coverity ID 937, REVERSE_INULLVolker Lendecke2009-09-041-2/+2
|
* s3:winbind: Fix Coverity ID 940: Resource LeakVolker Lendecke2009-09-041-0/+1
|
* ldb: ensure we cancel a ldb transactionAndrew Tridgell2009-09-042-3/+9
| | | | | | When we fail a ldbadd or ldbedit we should cancel the transaction to prevent ldb giving a warning about having a open transaction in the ldb destructor
* s4: fixed a missing NULL termination in a attribute list passed to ldb_searchAndrew Tridgell2009-09-041-1/+1
|
* report the location of the original talloc_free on double freetalloc-2.0.0Andrew Tridgell2009-09-041-11/+18
| | | | | | | | When we get a double free abort from talloc it is often hard to work out where the first free came from. This patch takes advantage of the fact that _talloc_free() now takes a location the free was called from to allow the double free abort code to print the location of the first free that conflicts.
* wbinfo: fix various valgrind warnings and an invalid free.Günther Deschner2009-09-041-7/+1
| | | | | | Kai, please check. Guenther
* s3-ntlm_auth: fix two segfaults in diagnostics mode.Günther Deschner2009-09-041-2/+2
| | | | Guenther
* Hopefully last part of the fix for bug 6651 - smbd SIGSEGV when breaking ↵Jeremy Allison2009-09-031-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | oplocks. This one is subtle. There is a race condition where a signal can be queued for oplock break, and then the file can be closed by the client before the signal can be processed. Currently if this occurs we panic (we can't match an incoming signal fd with a fsp pointer). Simply log the error (at debug level 10 right now, might be too much) and then return without processing the break request. It looks like there is another race condition with this fix, but here's why it won't happen. If the signal was pending (caused by a kernel oplock break from a local file open), and the client closed the file and then re-opened another file which happened to use the same file descriptor as the file just closed, then theoretically the oplock break requests could be processed on the wrong fd. Here's why this should be very rare.. Processing a pending signal always take precedence over an incoming network request, so as long as the client close request is non-chained then the break signal should always be harmlessly processed *before* the open can be called. If the open is chained onto the close, and the fd on the new open is the same as the old closed fd, then it's possible this race will occur. However, all that will happen is that we'll lose the oplock on this file. A shame, but not a fatal event. Jeremy.
* Another part of the fix for bug 6651 - smbd SIGSEGV when breaking oplocks.Jeremy Allison2009-09-031-2/+6
| | | | | | SA_INFO_QUEUE_COUNT *MUST* be a power of 2, in order for the ring buffer wrap to work correctly at the 32 bit boundary. Thanks to Petr Vandrovec <petr@vandrovec.name> for this.
* First attempt to implement dcesrv_drsuapi_DsGetNCChangesAnatoliy Atanasov2009-09-031-1/+204
| | | | | | | So far it returns the ctr6 responce without proper linked attributes support and metadata. A couple of improvements are the filter in the search uses '(uSNChanged>=N)', added extended dn search support, non-replicated attributes are excluded from the result.
* Fix the dsdb_syntax_OID_ldb_to_drsuapi functionAnatoliy Atanasov2009-09-031-1/+51
| | | | | | This replace the dsdb_syntax_FOOBAR_ldb_to_drsuapi function, which was left as a TODO code. Implementation in both added functions is completely identical and probably should differ in the future.
* Ignoring generated files:Kamen Mazdrashki2009-09-031-0/+2
| | | | | libcli/smb/smb_common_proto.h source4/torture/ntp/proto.h
* another large change to the linked_attribute moduleAndrew Tridgell2009-09-031-20/+64
| | | | | | | | | | | | | | | This one copes with deleted objects where linked attributes have been set on the module. We hit this when we do the ldb wipe at the start of a provision, which trigers linked attribute updates, but for objects that have disappeared. We need to ensure that the linked attribute updates only happen on the right object, and if the object gets re-created (as happens with a provision) then it is not the right object. To cope with this we record the GUID of the object when the operation that triggered the linked attribute update comes in, and then find the DN by suing that GUID when we apply the change in the prepare commit hook.
* hook on prepare_commit instead of transaction_endAndrew Tridgell2009-09-032-8/+11
| | | | This allows for safe transaction end aborts
* greatly simplify the transaction processing in the partition moduleAndrew Tridgell2009-09-031-51/+29
| | | | | Now that ldb is calling prepare commit separately, the job of the partition module on transaction end is much simpler (and more robust!)
* show more reasonable object counts during a vampireAndrew Tridgell2009-09-031-4/+18
| | | | | | | | | We now show the total number of objects we have processed, which gives the user a better idea of how much has been done. A vampire on a large domain can take an hour or more (which needs to be fixed btw, it is a problem with the lack of scalability of the ltdb index code). Watching the same msg for an hour makes you wonder if any progress is being made!
* always use prepare_commit in ldb transaction commits if possibleAndrew Tridgell2009-09-033-6/+51
| | | | | | | | | | The reason we need this is to make multi-tdb transactions safe, with the partition module. The linked_attributes and repl_meta_data modules now do extra processing when the transaction ends, and that processing can fail. When it fails we need to cancel the transaction, which we can only do if the hook is on the prepare commit instead of the end transaction call. Otherwise the partition module cannot ensure that no commit has been done on another partition.
generated by cgit (git 2.34.1) at 2025-09-25 15:54:28 +0000