summaryrefslogtreecommitdiffstats
path: root/source4
Commit message (Collapse)AuthorAgeFilesLines
* r2645: converted the NTLMSSP code to the new style of tallocAndrew Tridgell2007-10-107-107/+68
| | | | (This used to be commit b378aae95d4001c4cf4e6e59ed80ee1bd55382ee)
* r2644: removed an unused functionAndrew Tridgell2007-10-101-18/+0
| | | | (This used to be commit bc779cb2ce6bc13157f9d046400ce99d107ccd52)
* r2643: convert more of the auth subsyystem to the new talloc methods. ThisAndrew Tridgell2007-10-107-52/+35
| | | | | also fixes a memory leak found with --leak-check. (This used to be commit f19201ea274f0a542314c61c4af676197bf154ad)
* r2642: smb_iconv_t is a pointer, so checks against -1 errors should use a castAndrew Tridgell2007-10-101-1/+1
| | | | (This used to be commit 28dcd2202948b003f8d13951395baa4a722593f4)
* r2641: talloc_p() now produces a named talloc pointer, with the nameAndrew Tridgell2007-10-102-4/+32
| | | | | | | | | | auto-derived from the type you are allocating. This is done with basically zero overhead by relying on the stringify operator in cpp producing string constants. the result is that --leak-check nicely names all pointers that come from talloc_p() (This used to be commit bd86ebe2972af4d424df20db1e422919aa6203d0)
* r2640: valgrind does a great job on some types of memory leaks, but is slowAndrew Tridgell2007-10-102-5/+80
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and can't properly handle leaks of doubly linked lists which we use a lot (as the memory is always reachable). Even with --show-reachable its hard to track leaks down sometimes. I realised that talloc does have the necessary information to track these, and by using the cascading property of the new talloc it can report on leaks in a much more succinct fashion than valgrind can. I have added a new samba option --leak-check that applies to all Samba tools. When enabled it prints a leak report summarising all top level contexts that are present when the program exits. A typical report looks like this: talloc report on 'null_context' (total 1071 bytes in 52 blocks) iconv(CP850,UTF8) contains 43 bytes in 3 blocks UNNAMED contains 24 bytes in 1 blocks UNNAMED contains 24 bytes in 1 blocks dcesrv_init contains 604 bytes in 26 blocks server_service contains 120 bytes in 6 blocks UNNAMED contains 24 bytes in 1 blocks UNNAMED contains 24 bytes in 1 blocks server_service contains 104 bytes in 4 blocks server_context contains 12 bytes in 2 blocks iconv(UTF8,UTF-16LE) contains 46 bytes in 3 blocks iconv(UTF-16LE,UTF8) contains 46 bytes in 3 blocks the numbers are recursive summaries for all the memory hanging off each context. this option is not thread safe when used, but the code is thread safe if the option is not given, so I don't think thats a problem. (This used to be commit 96d33d36a5639e7fc46b14a470ccac674d87c62a)
* r2639: we doon't need the valid_table code, so get rid of itAndrew Tridgell2007-10-101-56/+0
| | | | (This used to be commit 480636ebbca102172621609496bdab682d4bda8a)
* r2638: do lazy initialisation of iconv handles, so we don't initialise aAndrew Tridgell2007-10-101-39/+29
| | | | | | | handle unless we use it. This saves quite a bit of memory (libc chews a lot loading a handle). Typically smbd now loads 3 handles, instead of 36. (This used to be commit 60e8d154fda548862cd6f8e8c1dadd64b3c4bd9c)
* r2635: mem_ctx cleanups on the lsa and netlogon pipes in the rpc serverAndrew Tridgell2007-10-103-50/+19
| | | | (This used to be commit 1ee5ed4197f49f12372835f66160801f19ee35a6)
* r2634: use discard_const_p() in a few placesAndrew Tridgell2007-10-105-10/+13
| | | | (This used to be commit 56ecda2178e33508c55c6195ccec41c06e099d6f)
* r2633: fixed some function types in the (unused) print backendAndrew Tridgell2007-10-101-2/+2
| | | | (This used to be commit e9803058ecc0b0f849aee48a077bff4e2c8feaa5)
* r2632: a new approach to handling const errors. We have had huge numbers ofAndrew Tridgell2007-10-103-2/+24
| | | | | | | | | | | | | | | const warnings for a long time, and no real way to approach a solution. Some of them are unavoidable due to the way the C standard works (for example, any function that provides strchr() like functionality _must_ produce a const warning) I will be converting a bunch of places that currently produce const warnings to use the discard_const_p(). Some of these will be unavoidable const problems, some of them will be ones we will fix up over time. At least this change means we will no longer be swamped with const warnings, and we will easily be able to see when new problems emerge. (This used to be commit fec3288ad6ce58e8273e3f16e88037db49ecf046)
* r2631: the strchr family of functions should not return const strings.Andrew Tridgell2007-10-101-3/+3
| | | | (This used to be commit 2a7e5f07086ef4aebbb2be35acbf9c7c39b13c75)
* r2630: I missed a couple of places in the gensec talloc conversionAndrew Tridgell2007-10-101-3/+3
| | | | (This used to be commit 7124949140141513193f41bb8491aa6a283efed7)
* r2629: convert gensec to the new talloc modelAndrew Tridgell2007-10-1013-45/+40
| | | | | | | by making our gensec structures a talloc child of the open connection we can be sure that it will be destroyed when the connection is dropped. (This used to be commit f12ee2f241aab1549bc1d9ca4c35a35a1ca0d09d)
* r2628: got rid of some warnings and converted a few more places to use ↵Andrew Tridgell2007-10-108-15/+17
| | | | | | hierarchical memory allocation (This used to be commit 26da45a8019a2d6c9ff2ac2a6739c7d0b42b00de)
* r2627: use the new talloc capabilities in a bunch more places in the rpcAndrew Tridgell2007-10-1011-94/+64
| | | | | | | | server code. This fixes a number of memory leaks I found when testing with valgrind and smbtorture, as the cascading effect of a talloc_free() ensures that anything derived from the top level object is destroyed on disconnect. (This used to be commit 76d0b8206ce64d6ff4a192979c43dddbec726d6e)
* r2626: the symbol gai_error is defined in /usr/include, so don't use that ↵Andrew Tridgell2007-10-101-4/+4
| | | | | | name in our code (This used to be commit 458f85328850905db8e9808d02898c69b5f9b872)
* r2625: use talloc_p, not talloc when possible (when allocating a structure ↵Andrew Tridgell2007-10-101-1/+1
| | | | | | in particular), as it gives us type checking. (This used to be commit dabc7ddd9f940db414d1c3c7bf3cebcd108fbf6f)
* r2624: - save some system calls by only trying read/write operations that ↵Andrew Tridgell2007-10-101-1/+11
| | | | | | | select has indicated are possible - when a socket is dead, don't try to do anything more on it (This used to be commit e95e5c591fcf9c3b7fde7fbdcc1837e22195e0a8)
* r2623: don't do pointer arithmetic on void*, as it doesn't work with non-GNU ↵Andrew Tridgell2007-10-101-1/+1
| | | | | | compilers (This used to be commit c2be7b696ccb338df06a5212ed1f7b78e4c116c2)
* r2622: to implement the SOCKET_FLAG_BLOCK option in the socket library weAndrew Tridgell2007-10-101-0/+4
| | | | | | need to add MSG_WAITALL to the recv() flags. This is needed by the current server code or sometimes it will fail with a receive error. (This used to be commit 4cb11fb77acf74ab53bf5782a114151965c558f0)
* r2621: - now that the client code is non-blocking, we no longer needAndrew Tridgell2007-10-103-93/+2
| | | | | | | write_data and read_data, which are inherently blocking operations - got rid of some old NBT keepalive routines that are not needed (This used to be commit e73b4ae4e500d3b7ee57e160e0f8b63c99b2542a)
* r2618: before we had refererence counts in talloc I added a hack in theAndrew Tridgell2007-10-105-23/+8
| | | | | | | server side request structure to prevent a structing being freed in some circumstances. This change replaces this with the much more robust mechanism of talloc_increase_ref_count(). (This used to be commit 3f7741f178b359f81cc98ef18cd69bf976123e9f)
* r2617: add connect testing to the rpc test suiteAndrew Tridgell2007-10-101-1/+1
| | | | (This used to be commit 01a759b62775b447eeb2ad447b12d104caa9bfb4)
* r2616: the cascading nature of talloc_free() can lead to some surprises. InAndrew Tridgell2007-10-101-0/+1
| | | | | | | | this case the bug was that server_terminate_connection() destroys the server context, which in turn cascades down to destroy all current request contexts, so we musn't then try to destroy the request structure a second time. (This used to be commit 28a647f681e2166c01f7ac59b16305676d5caa71)
* r2615: fixed a bug in the server side support for CONNECT level securityAndrew Tridgell2007-10-101-6/+12
| | | | (This used to be commit fee98137ad6358195b80c97cd6cc8f82ac53f870)
* r2614: support CONNECT level DCE/RPC security in both client andAndrew Tridgell2007-10-105-23/+108
| | | | | | | server. CONNECT security uses NTLMSSP, but does not do any signing or sealing (or equivalently, its like signing, but with a zero filled checksum). (This used to be commit f4660857bc708db7f5aa7487bf7ab04bffe68928)
* r2613: use a talloc destructor to ensure that file descriptors are not leakedAndrew Tridgell2007-10-101-2/+26
| | | | | | | | | | | on abnormal termination of a connection. As long as the top level connection structure is freed then that should cascade down to the file structure, and call this destructor which will close the open file descriptor. In general I'd like to use this technique in any place in Samba4 where we hold operating system resources that we need to make sure are released on abnormal termination. (This used to be commit ed87b7fcbd9fedc155528ce6dd8ab5d5fce637b2)
* r2612: Ensure ntlm_auth always logs to stderr.Andrew Bartlett2007-10-101-2/+2
| | | | | | | Add missing break; Andrew Bartlett (This used to be commit cdb8261775a3100e1b95b485d91ba1f94c879905)
* r2611: Try to make Samba4's ntlm_auth more consistant with Samba 3.0.Andrew Bartlett2007-10-101-8/+5
| | | | | Andrew Bartlett (This used to be commit 8f4dab5d44480b40fc14afc70172861c229ba77d)
* r2601: avoid free()ing unallocated memory by mistakeSimo Sorce2007-10-101-1/+6
| | | | (This used to be commit e502b276ae5e4e22e31a522c4d9e346996d6e29f)
* r2597: A small program that takes SID strings on stdin and produces a marshalledTim Potter2007-10-103-0/+93
| | | | | lsa_SidArray on stdout. (This used to be commit d7d8a7ffc66cf6f78f11e8aed975d746c7a520a3)
* r2594: Remove call to Gtk+ 2.4 specific codeJelmer Vernooij2007-10-101-25/+8
| | | | (This used to be commit fa29cecb12def7f5c74dbcd9a525a858323e6327)
* r2593: don't crash if the server doesn't know that 0 count searches mean 1Andrew Tridgell2007-10-101-2/+6
| | | | (This used to be commit 640ced453092a5c5f3ffe7ee0fe4be804a4ced14)
* r2592: this fixes one of the security memory leaks in the serverAndrew Tridgell2007-10-101-1/+1
| | | | (This used to be commit efb2b88edddef94ecbaa9a871d457d0d7c177546)
* r2591: fixed two errors in simple backend found with valgrindAndrew Tridgell2007-10-101-0/+2
| | | | (This used to be commit 1730882b9d2ecff1b65e5fc85961edb300a9ce17)
* r2590: fixed one of the server security memory leaks. There are more :(Andrew Tridgell2007-10-101-0/+4
| | | | (This used to be commit 9e1eb58e4b332e4a300e8b546a5d39bd2f7cd7a6)
* r2589: a simple test to help find security related memory leaks. Run ↵Andrew Tridgell2007-10-103-1/+71
| | | | | | | valgrind on smbd with --show-leak=yes and --show-reachable=yes to track them down. (This used to be commit 7b23624a0f50c29346e8b1c4057f1c21f3be6d5a)
* r2588: connect/disconnect is common enough that I don't think a level 0 DEBUGAndrew Tridgell2007-10-103-3/+3
| | | | | is warranted to warn that it has happened :) (This used to be commit ee51eefe17576496dfd091ed7e7783caff574090)
* r2587: fixed a couple of authentication memory leaks. There are more to beAndrew Tridgell2007-10-103-2/+9
| | | | | fixed - I'll commit a little test suite soon. (This used to be commit 5b967c1cbb9831f7f2c6c6187f9e8e6dcc284497)
* r2586: updated the nbench example in the README to reflect the new chaining ↵Andrew Tridgell2007-10-101-2/+1
| | | | | | syntax (This used to be commit be20b3164cfe1d5c228072722cb6e5894fdacb23)
* r2583: mkproto.pl now treats "int main" as a special case and avoids it.Andrew Tridgell2007-10-101-0/+2
| | | | (This used to be commit 01288e82bc39af66d5e47db19691c741555e999a)
* r2582: Merge checks for xattr and acl libraries from Samba3 so the ↵Tim Potter2007-10-104-2/+149
| | | | | | | {get,set}ntacl programs can build on non-xattr machines. (This used to be commit daad76207dbb4060c231a58c99970e837e1e858f)
* r2581: added "hosts allow" and "hosts deny" checking in smbd. I needed thisAndrew Tridgell2007-10-107-0/+398
| | | | | | | | | | | | | as my box keeps getting hit by viruses spreading on my companies internal network, which screws up my debug log badly (sigh). metze, I'm not sure if you think access.c should go in the socket library or not. It is closely tied to the socket functions, but you may prefer it separate. The access.c code is a port from Samba3, but with some cleanups to make it (slighly) less ugly. (This used to be commit 058b2fd99e3957d7d2a9544fd27071f1122eab68)
* r2580: fixed an uninitialised byte found by valgrindAndrew Tridgell2007-10-101-2/+2
| | | | (This used to be commit 0806378b0e34ba3d665a9db739539819f3f52054)
* r2577: - I recently found out that charaters below 0x3F are guaranteed not toAndrew Tridgell2007-10-102-45/+58
| | | | | | | | | | occur as secondary bytes in any multi-byte character set. This allows for a very simple optimisation in strchr_m() and strrchr_m(). It might be a good idea to pick this up for Samba3. - the horrible toktocliplist() is only used in clitar.c, so move it there, to prevent anyone else from being tempted to use it. (This used to be commit 663b7b75ddd838ce547425b07d7ce4d4606fb479)
* r2576: Some userspace tools for getting and setting ntacls via the ↵Tim Potter2007-10-104-0/+252
| | | | | | | 'security.ntacl' extended attribute. (This used to be commit 5b88226f9002711baac73e66d04ecf92b7765809)
* r2573: - added a configure test for nanosecond time resolution in struct statAndrew Tridgell2007-10-105-26/+56
| | | | | | | | | | | (recently Linux systems support this, allowing us to support the full resolution in NTTIME) - use nanosecond resolution in the posix backend if available - moved the configure tests and list of object files for the posix backend into ntvfs/posix/ to keep them more neatlly separated. (This used to be commit d92ad9f307fe16a3b253a0555b437f14c94b4dd7)
* r2572: fixed two places where status is not initialised in the nbench backendAndrew Tridgell2007-10-101-2/+2
| | | | (This used to be commit 4103392a597349890e0e7ea1c41d5b0ab3816853)
generated by cgit (git 2.34.1) at 2024-11-11 11:37:05 +0000