summaryrefslogtreecommitdiffstats
path: root/source/utils
Commit message (Collapse)AuthorAgeFilesLines
...
* use GET_DENY_MODE() macroAndrew Tridgell2000-01-161-2/+1
|
* added code to allow traversal of the byte range lock databaseAndrew Tridgell2000-01-161-1/+29
| | | | this is used with "smbstatus -B" to dump the lock list
* casts and defines to make solaris happyAndrew Tridgell2000-01-142-3/+3
|
* we now pass all byte range locking testsAndrew Tridgell2000-01-141-14/+12
| | | | | the last piece was to use a smb timeout slightly larger than the locking timeout in bloking locks to prevent a race
* some more work on the byte range lockingAndrew Tridgell2000-01-141-14/+16
| | | | | | | | note the ugly global_smbpid - I hope that won't bethere for long, I just didn't want to do two lots of major surgery at the one time. Using global_smbpid avoids the big change of getting rid of our inbuf/outbuf interface to reply routines. I'll do that once the locking stuff passes all tests.
* greatly expanded the lock4 locking test. we now pass all but one testAndrew Tridgell2000-01-131-45/+93
| | | | - that should be fixed soon.
* I'm currently designing a new locking system (using a tdb database!)Andrew Tridgell2000-01-101-21/+129
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | that will make us match NT semantics exactly and do away with the horrible fd multiplexing in smbd. this is some diag stuff to get me started. - added the ability to do read or write locks in clientgen.c - added a LOCK4 test to smbtorture. This produces a report on the server and its locking capabilities. For example, NT4 gives this: the same process cannot set overlapping write locks the same process can set overlapping read locks a different connection cannot set overlapping write locks a different connection can set overlapping read locks a different pid cannot set overlapping write locks a different pid can set overlapping read locks the same process can set the same read lock twice the same process cannot set the same write lock twice the same process cannot override a read lock with a write lock the same process can override a write lock with a read lock a different pid cannot override a write lock with a read lock the same process cannot coalesce read locks this server does strict write locking this server does strict read locking whereas Samba currently gives this: the same process can set overlapping write locks the same process can set overlapping read locks a different connection cannot set overlapping write locks a different connection can set overlapping read locks a different pid can set overlapping write locks a different pid can set overlapping read locks the same process can set the same read lock twice the same process can set the same write lock twice the same process can override a read lock with a write lock the same process can override a write lock with a read lock a different pid can override a write lock with a read lock the same process can coalesce read locks this server does strict write locking this server does strict read locking win95 gives this - I don't understand why! the same process cannot set overlapping write locks the same process cannot set overlapping read locks a different connection cannot set overlapping write locks a different connection cannot set overlapping read locks a different pid cannot set overlapping write locks a different pid cannot set overlapping read locks the same process cannot set the same read lock twice the same process cannot set the same write lock twice the same process cannot override a read lock with a write lock the same process cannot override a write lock with a read lock a different pid cannot override a write lock with a read lock the same process cannot coalesce read locks this server does strict write locking this server does strict read locking
* extent smbtorture to test with both an exe file and a dat fileAndrew Tridgell2000-01-081-37/+43
|
* cli_open() wasn't handling DENY_FCB or O_WRONLY correctly.Andrew Tridgell2000-01-081-1/+1
| | | | | | After fixing that I needed to use O_RDWR instead of O_WRONLY in several places to avoid the silly bug in MS servers that doesn't allow getattrE on a file opened with O_WRONLY
* added a DENY test that tests deny mode handling. It produces a matrixAndrew Tridgell2000-01-081-2/+86
| | | | | of 324 lines (6*6*3*3) of all possible deny mode behaviour. This allows us to compare with NT. We currently don't match :)
* this looks like a big commit, but it isn't really :)Andrew Tridgell2000-01-072-8/+8
| | | | | | | | This fixes our netbios scope handling. We now have a 'netbios scope' option in smb.conf and the scope option is removed from make_nmb_name() this was prompted by a bug in our PDC finding code where it didn't append the scope to the query of the '*' name.
* added the unexpected packet database (unexpected.tdb)Andrew Tridgell2000-01-031-4/+4
| | | | | | | | | | | | this means "nmblookup -S" now always works, even with broken servers the database stores all unexpected replies and these can be accessed by any client. while doing this I cleaned up a couple of functions, and put in place a better trn_id generator. in most places the code got quite a bit simpler due to the addition of simple helper functions. I haven't yet put the code in to take advantage of this for pdc replies - that will be next. Jeremys pdc finding code will then work :)
* - added tdb_flags option to tdb_open()Andrew Tridgell2000-01-021-4/+4
| | | | | | | | | - added TDB_CLEAR_IF_FIRST flag to clear the database if this is the first attached process. Useful for non-persistent databases like our locking area (this will also make upgrades to new database layouts easier) - use lock_path() in a couple of places - leave connections database open while smbd running - cleaned up some tdb code a little, using macros for constants
* improved error message in case the lock list is truncatedAndrew Tridgell1999-12-221-1/+8
|
* changed message is connections.tdb doesn't existAndrew Tridgell1999-12-211-1/+1
|
* converted all our existing shared memory code to use a tdb databaseAndrew Tridgell1999-12-211-24/+9
| | | | | | | | | | | | | instead of either sysv or mmap shared memory or lock files. this means we can now completely remove locking_shm.c locking_slow.c shmem.c shmem_sysv.c and lots of other things also got simpler locking.c got a bit larger, but is much better compartmentalised now
* first cut at using the tdb code for the connections structure, theAndrew Tridgell1999-12-211-192/+192
| | | | | SWAT status page and smbstatus. It made the code _much_ simpler, I wish we'd done a database module a long time ago!
* this was left out from the 2.0.6 mergeAndrew Tridgell1999-12-211-0/+236
|
* more files from 2.0.6Andrew Tridgell1999-12-171-0/+308
|
* 2nd phase of head branch sync with SAMBA_2_0 - this delets all the files ↵Andrew Tridgell1999-12-132-680/+0
| | | | that were in the head branch but weren't in SAMBA_2_0
* first pass at updating head branch to be to be the same as the SAMBA_2_0 branchAndrew Tridgell1999-12-1311-1534/+1224
|
* final part of "first" phase converting over to msrpc daemon architecture.Luke Leighton1999-12-121-2/+0
| | | | | | | | | | | | done a minimal amout of clean-up in the Makefile, removing unnecessary modules from the link stage. this is not complete, yet, and will involve some changes, for example to smbd, to remove dependencies on the password database API that shouldn't be there. for example, smbd should not ever call getsmbpwXXX() it should call the Samr or Lsa API. this first implementation has minor problems with not reinstantiating the same services as the caller. the "homes" service is a good example.
* OK. This code works on a RedHat 6.0 system. However smbpasswdGerald Carter1999-12-091-0/+2
| | | | | | | | | | | | | | | | | time out of sending the session setup on Solaris 2.6. No idea. I'll work on it some tomorrow. This is to fix the "Unable to setup password vectors" thingy. Also changed an inet_aton() to inet_addr() as the former is not very portable :-) Luke, I set the redir flag to false because the connection to the smb-agent was failing and smbpasswd bombed. Double check me on this one. -jc
* ABOUT TIME!!!!!!!!Luke Leighton1999-12-081-41/+28
| | | | | | | | | | | | | | | damn, this one is bad. started, at least two days ago, to add an authentication mechanism to the smbd<->msrpc redirector/relay, such that sufficient unix / nt information could be transferred across the unix socket to do a become_user() on the other side of the socket. it is necessary that the msrpc daemon inherit the same unix and nt credentials as the smbd process from which it was spawned, until such time as the msrpc daemon receives an authentication request of its own, whereupon the msrpc daemon is responsible for authenticating the new credentials and doing yet another become_user() etc sequence.
* created create_pipe_socket() function.Luke Leighton1999-12-052-94/+5
|
* argh! how horrible! spent ages working out why packets weren't beingLuke Leighton1999-12-041-7/+10
| | | | | | | | | | | | | | | | | | | | | | | | received properly when a UDP "retry" occurs. it's because reads and writes must be interleaved / matched. scenario: nmblookup connects to agent, sends request. agent receives request, broadcasts it on 137. agent RECEIVES 137 broadcast, sends it to nmblookup agent receives RESPONSE to 137 broadcast, sends it to nmblookup. if reads are not equally interspersed with writes, then second send will fail. if you think this is odd behaviour and that the agent should be filtering its own UDP traffic, think again. agent will be, potentially, redirecting nmbd traffic (including WINS server) not just client programs.
* even more cool! nmb-agent moved over to new vagent style, too!Luke Leighton1999-12-041-229/+46
|
* cool! created higher-order function table for agent redirection.Luke Leighton1999-12-041-216/+37
|
* more similar agent codeLuke Leighton1999-12-042-47/+43
|
* nmb agent memory free problemsLuke Leighton1999-12-041-7/+6
|
* trying to make redirector agent code same base.Luke Leighton1999-12-042-62/+78
|
* jeremy is going to hate me for this.Luke Leighton1999-12-042-11/+530
| | | | | | | | | | | created an "nmb-agent" utility that, yes: it connects to the 137 socket and accepts unix socket connections which it redirects onto port 137. it uses the name_trn_id field to filter requests to the correct location. name_query() and name_status() are the first victims to use this feature (by specifying a file descriptor of -1).
* argh! you wouldn't believe what i had to do: use the mid (multiplex id)Luke Leighton1999-12-041-14/+96
| | | | | | to redirect multiple socket-based connnections onto a single client state. argh!
* argh! smb-agent redirection client reusage is a nightmare!Luke Leighton1999-12-031-143/+225
| | | | | | moved smb-agent over to a single-process model instead of fork() in order to reuse client connections. except, of course, you can't do a select() on the same socket connections! argh!
* starting "connection reuse" system in smb-agent. added version numberLuke Leighton1999-12-031-74/+122
| | | | which isn't actually used right now :-)
* smb-agent improvements. added -D (daemon) option. smb agent isLuke Leighton1999-12-031-16/+72
| | | | | restricted to connections from the current user (socket is created with current user uid).
* cool! a unix socket smb redirector. code based on smbfilter andLuke Leighton1999-12-031-0/+347
| | | | | | | | ideas from ssh-agent. the intent is to be able to share smb sessions using cli_net_use_add() across multiple processes, where one process knows the target server name, user name and domain, but not the smb password.
* fixing joining to domain plus something weird going down with nt logins...Luke Leighton1999-12-011-33/+0
|
* sys_select added one more argument (read, write selectors).Luke Leighton1999-12-011-2/+2
|
* first stages of removing struct cli_state* and uint16 fnum from allLuke Leighton1999-11-241-11/+3
| | | | | | | | | msrpc client code. the intent is to hide / abstract / associate connection info behind policy handles. this makes the msrpc functions look more and more like their nt equivalents. who-hou!
* attempting to establish inter-domain trust relationships. modifiedLuke Leighton1999-11-201-28/+115
| | | | smbpasswd so it can be used to set up inter-domain trust account.
* event log update, netsessenum, netconnenum update.Luke Leighton1999-08-181-2/+2
|
* patch from Michael Glauche to call get_status_connections() instead ofLuke Leighton1999-08-181-52/+52
| | | | reading STATUS..LCK direct.
* BDC support.Matthew Chapman1999-07-221-32/+38
| | | | Added -S (Synchronise) option to smbpasswd, which calls synchronise_passdb.
* BDC support.Luke Leighton1999-07-211-5/+21
|
* improving authentication code (tidyup).Luke Leighton1999-06-291-0/+2
|
* safe string error reporting functions (found a potential buffer overflowLuke Leighton1999-06-241-1/+1
| | | | of a pstrcpy into an fstring).
* variation of random SMBtrans2. random delays in between reconnectionsLuke Leighton1999-05-071-10/+12
| | | | | increased. size of large random buffer decreased. number of reconnection attempts increased.
* had to move day display names into lib/util, to get rpctorture to compile.Luke Leighton1999-05-071-3/+5
|
* open_socket_in() takes a different number of parameters in the headAndrew Tridgell1999-04-171-1/+1
| | | | branch. We need that merge soon!
generated by cgit (git 2.34.1) at 2025-09-28 21:57:59 +0000