summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* s3:smbd: add marshalling layer for SMB2 Break support (SMB 2.002 only)Stefan Metzmacher2009-07-024-1/+217
| | | | metze
* s3:smbd: add marshalling layer for SMB2 SetInfo supportStefan Metzmacher2009-07-024-1/+222
| | | | metze
* s3:smbd: add marshalling layer for SMB2 GetInfo supportStefan Metzmacher2009-07-024-1/+261
| | | | metze
* spoolss: the flags in spoolss_PrinterInfo1 are in fact ↵Günther Deschner2009-07-024-55/+55
| | | | | | spoolss_PrinterAttributes. Guenther
* s4-smbtorture: fix getjob test in RPC-SPOOLSS.Günther Deschner2009-07-021-0/+5
| | | | Guenther
* doserrors: print out some more werrors.Günther Deschner2009-07-021-0/+5
| | | | Guenther
* talloc: change TALLOC_MAGIC for version 2.0.0Stefan Metzmacher2009-07-021-1/+12
| | | | metze
* show attribute values in sorted order to make comparison easierAndrew Tridgell2009-07-021-0/+5
|
* s3:smbd: add support for SMB2 NotifyStefan Metzmacher2009-07-024-1/+378
| | | | metze
* s3:smbd: make change_notify_reply() more generic and hide send_nt_replies() ↵Stefan Metzmacher2009-07-023-17/+42
| | | | | | | | behind a callback This prepares change notify support for SMB2. metze
* s3:smbd: simplify the notify code a bit and always reply via ↵Stefan Metzmacher2009-07-023-35/+30
| | | | | | change_notify_reply() -> send_nt_replies() metze
* s3:smbd: push nttrans and trans2 responses with no data to the clientStefan Metzmacher2009-07-022-0/+16
| | | | | | | | | | For sync replies it's not a problem, as construct_reply() will send the response, but for async replies we would not send the reply to the client. Currently the notify code works arround this manually, so I assume we didn't have a bug here. But the next commits will simplify the notify code. metze
* s3:smbd: restore the 3.0.x bahavior of send_nt_replies()Stefan Metzmacher2009-07-021-0/+5
| | | | | | We should also set the error code, when we return no parameters or data. metze
* s3:smbd: move global notify_changes_by_mid to smbd_server_connectionStefan Metzmacher2009-07-023-7/+8
| | | | metze
* s3:smbd: allow the offset to the path being 0 in SMB2 createStefan Metzmacher2009-07-021-1/+3
| | | | metze
* we can't use the unique index code for samAccountNameAndrew Tridgell2009-07-022-8/+75
| | | | | | | | | | Using ldb unique indexes for samAccountName doesn't work with DRS as the other DC may send us a deleted record (tombstone record), which has the same samAccountName as an existing record. That would then create two records in the same partition with the same samAccountName. So we needed to put back the logic in samldb.c which explicitly checked whether a samAccountName already exists on add
* decrypt all objects in a DRS record, not just the first oneAndrew Tridgell2009-07-021-2/+5
| | | | | We found this as an object came across from w2k3 with zero values, which caused a segv when we tried to decrypt the first value
* change talloc to 2.0.0Andrew Tridgell2009-07-023-3/+3
| | | | | | | This is needed to prevent samba3 and samba4 from using an ABI incompatible system version of talloc See ongoing discussion on the samba-technical mailing list
* Changed ldb.ERR_NO_SUCH_OBJECT to LDB_ERR_NO_SUCH_OBJECT.Andrew Tridgell2009-07-021-5/+5
| | | | | | | | The LDB_ERR_NO_SUCH_OBJECT varient is not a defined variable. This should improve error handling in our python code on some systems. Unfortunately it still doesn't work on mine. I need to trap Jelmer somewhere where he can't escape some day and force him to divulge the deep druid secrets of python exception handling ....
* fixed the pull of drs schema elementsAndrew Tridgell2009-07-023-33/+108
| | | | | | | | The previous code incorrectly assumed that attributes such as subClassOf come over the wire as strings. In fact they come over as 32 bit integers which refer to goversIDs. We have to post-process these as it sometimes happens that a governsID comes over the wire before the record that defines what it means.
* the settings structure needs to be initialisedAndrew Tridgell2009-07-021-0/+1
|
* LDB_ERR_INVALID_DN_SYNTAX doesn't exist ...Andrew Tridgell2009-07-021-1/+1
| | | | The correct name is ldb.ERR_INVALID_DN_SYNTAX
* s4:param use talloc_unlink() to free iconv context holding referencesAndrew Bartlett2009-07-021-1/+1
|
* [SAMBA 4 directory] Changes "forceLogoff" and corrects the "subRefs"Matthias Dieter Wallnöfer2009-07-021-2/+4
| | | | | | | - This changes the attribute "forceLogoff" to its' default values according to Windows Server 2003 R2 - Also this corrects the "subRefs" attribute of the base-DN which only refers to direct child partitions (and therefore not to the complete transitive closure)
* Ensure we don't use delayed writes on POSIX opened files.Jeremy Allison2009-07-012-0/+15
| | | | | | Don't remove pending writetime changes if no time changes are sent in UNIX_BASIC infolevel. Jeremy
* Fix bug #6520 time stamps - e.g. last mod time is not preserved when "unix ↵Jeremy Allison2009-07-011-3/+31
| | | | | | | | extensions=yes" are set - and using latest cifs vfs client Cancel out any pending "sticky" writes or "last write" changes when doing a UNIX info level set. Jeremy.
* s3:util: let parent_dirname() correctly return toplevel filenamesStefan Metzmacher2009-07-011-1/+1
| | | | metze
* s3:onefs_open: remove unused variable passed to parent_dirname()Stefan Metzmacher2009-07-011-2/+1
| | | | metze
* s3:smbd: remove unused variables passed to parent_dirname()Stefan Metzmacher2009-07-012-5/+3
| | | | metze
* s3:build: remove the libgpo objects upon "make clean"Michael Adam2009-07-011-1/+2
| | | | Michael
* s3:build: remove ../libcli/nbt/tools/nmblookup.o and friends in make cleanMichael Adam2009-07-011-1/+1
| | | | Michael
* lib/util: fix order of includes in tevent_ntstatus.cMichael Adam2009-07-011-1/+1
| | | | | | replace.h needs to be included first. Michael
* fixed the talloc testsuite for the recent changesAndrew Tridgell2009-07-011-6/+10
|
* a talloc_realloc() to zero size needs to use an unambiguous freeAndrew Tridgell2009-07-011-1/+1
|
* s3/docs: Fix typo.Matt Kraai2009-07-011-1/+1
| | | | This fixes bug #6519.
* removed a generated fileAndrew Tridgell2009-07-011-74/+0
|
* use a talloc_reparent in a very ugly wayAndrew Tridgell2009-07-011-2/+11
| | | | this works around some terrible use of talloc in the libnet code
* use the new talloc_reparent in two placesAndrew Tridgell2009-07-012-2/+2
|
* changes to remove the ambiguity in talloc_free() and talloc_steal() Andrew Tridgell2009-07-012-26/+109
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These changes follow from the discussions on samba-technical. The changes are in several parts, and stem from the inherent ambiguity that was in talloc_free() and talloc_steal() when the pointer that is being changes has more than one parent, via references. The changes are: 1) when you call talloc_free() on a pointer with more than one parent the free will fail, and talloc will log an error to stderr like this: ERROR: talloc_free with references at some/foo.c:123 reference at other/bar.c:201 reference at other/foobar.c:641 2) Similarly, when you call talloc_steal() on a pointer with more than one parent, the steal will fail and talloc will log an error to stderr like this: ERROR: talloc_steal with references at some/foo.c:123 reference at other/bar.c:201 3) A new function talloc_reparent() has been added to change a parent in a controlled fashion. You need to supply both the old parent and the new parent. It handles the case whether either the old parent was a normal parent or a reference The use of stderr in the logging is ugly (and potentially dangerous), and will be removed in a future patch. We'll need to add a debug registration function to talloc.
* gensec_start now steals the auth_contextAndrew Tridgell2009-07-011-1/+3
|
* A rather strange varient of talloc_unlinkAndrew Tridgell2009-07-011-1/+1
| | | | | | A dcerpc request may have a reference from a still completing async callback, but we now consider the request to be complete. We want to lose the main parent, leaving just the reference, if any.
* another case that should use py_talloc_referenceAndrew Tridgell2009-07-011-1/+1
|
* use py_talloc_reference instead of py_talloc_importAndrew Tridgell2009-07-011-1/+1
| | | | | This is one of the few cases where we want the object to be owned by both the python object and C code
* py_talloc_import now uses a steal, so this free is incorrectAndrew Tridgell2009-07-011-1/+0
|
* fixed use of reference in pytallocAndrew Tridgell2009-07-012-3/+24
| | | | | | | | | | | | The previous code caused memory leaks, and also caused situations where talloc_free could be called on pointers with multiple parents The new approach is to have two functions: py_talloc_import : steals the pointer, so it becomes wholly owned by the python object py_talloc_reference: uses a reference, so it is owned by both python and C
* use a talloc_unlink() as ops may have a referenceAndrew Tridgell2009-07-011-1/+1
|
* fixed the reference to the global_schemaAndrew Tridgell2009-07-011-2/+3
|
* removed a redundent talloc_stealAndrew Tridgell2009-07-011-2/+0
|
* fixed the use of talloc_steal in ntlmssp_server Andrew Tridgell2009-07-011-3/+2
| | | | | The previous use of talloc_steal could cause a steal of a pointer that had references. This ensures that doesn't happen
* fixed rpc smb code to not reply on talloc_free being a function pointerAndrew Tridgell2009-07-012-2/+13
| | | | | | The upcoming talloc_free/talloc_reference changes change talloc_free to be a macro. These two bits of code relied on it being a function pointer
generated by cgit (git 2.34.1) at 2025-09-26 10:29:13 +0000