| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
the wrong place in smbencrypt.c.
|
| |
|
|
|
|
|
|
|
| |
perl -e 's/bzero\((.*),\s*sizeof\(\*\1\)\)/ZERO_STRUCTP($1)/g' -pi */*.c
perl -e 's/bzero\((.*),\s*sizeof\(\1\)\)/ZERO_STRUCT($1)/g' -pi */*.c
perl -e 's/bzero\(&(.*),\s*sizeof\(\1\)\)/ZERO_STRUCT($1)/g' -pi */*.c
perl -e 's/bzero\((.*),(.*)\)/memset($1, 0, $2)/g' -pi */*.c
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Date: Mon, 27 Mar 2000 20:37:20 +0200
From: Elrond <Elrond@Wunder-Nett.org>
To: Luke Kenneth Casson Leighton <lkcl@samba.org>
Subject: lsarpcd: more lookupsids
- lib/set_uid.c some reindenting.
- libsmb/clientgen.c:get_any_dc_name():
"We" are also responsible for "Builtin", right?
- parse_lsa, cli_lsa.c: The dom_refs were marshalled
incorrectly (the names and sids were put in the wrong
slot.)
- minor cleanup
- lib/util_sid.c: minor try to merge from HEAD, please
don't indent it!
Elrond
|
|
|
|
| |
nmbd/*.c over. a few issues left to deal with...
|
| |
|
|
|
|
| |
global_myname
|
|
|
|
|
|
| |
2) logon to local workstation when it is a member of a domain is also
allowed, by making domain_client_validate accept our own localservername
as the domain name (a la MYSERVERNAME\user)
|
| |
|
|
|
|
| |
in passwords. AAGH!
|
|
|
|
|
| |
out by receiving little-endian DCE/RPC packets and sending big-endian
DCE/RPC packets, of course the POLICY_HND was wrong...
|
|
|
|
|
| |
cli_samr.c. from the NetrSamLogon the first 8 bytes of the
LM# are received, i forgot to pass this over.
|
|
|
|
|
|
| |
added decls for setresuid.
const issues.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Date: Wed, 23 Feb 2000 19:28:08 +0100
From: Elrond <Elrond@Wunder-Nett.org>
To: Luke Kenneth Casson Leighton <lkcl@samba.org>
Subject: receiving multiple pdus
Hi Luke,
Someone ran rpcclients enumusers against a 2500 user domain
yesterday... and it crashed...
The code to receive multiple pdus is broken...
I fixed most of the things, I could find out myself, but in
rpc_client/cli_connect.c:rpc_api_rcv_pdu() in the
MSRPC_LOCAL-case, I don't know, what you wanted there.
(ret = ...; ret = ...;)
What I did:
- fixed receiving of multiple pdus
(now you should be able to run rpcclient against your
favorite 2500 user domain)
- fixed some possible problem in become_guest
(I realy should write something to samba-technical, this
one is possibly interesting for HEAD/2.0 too)
- fixed up some copyrights (I know, I modified those)
Elrond
[lkcl: the code that elrond fixed was to read a dce/rpc header of
0x18 bytes. i _thought_ i'd removed this code and replaced it
with read-an-entire-pdu. it _is_ ok to do this, because the last
pdu turns up short when using SMBs. you request 0x1630 bytes and
you only get... say.... 0x40, 0x18 of which is the header and the
rest is the last part of the last PDU]
|
|
|
|
|
|
|
| |
turns out that they use a different format for the $MACHINE.ACC
secrets.
AGH!
|
|
|
|
|
|
| |
const issues in credentials.c / cli_login.
make proto
|
| |
|
| |
|
| |
|
|
|
|
|
| |
store the pipe name in the ncacn_np struct so that the re-use search
could FIND the damn thing to actually reuse it).
|
|
|
|
| |
unnecessary.
|
|
|
|
| |
shouldn't be leaving out the length bit, that's kinda-needed!
|
| |
|
| |
|
|
|
|
| |
found a bug in lsa_open_pol2().
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
two places i found where it was appropriate to _use_ that third argument,
in locking.c and brlock.c! there was a static traverse_function and
i removed the static variable, typecast it to a void*, passed it to
tdb_traverse and re-cast it back to the traverse_function inside the
tdb_traverse function. this makes the use of tdb_traverse() reentrant,
which is never going to happen, i know, i just don't like to see
statics lying about when there's no need for them.
as i had to do in samba-tng, all uses of tdb_traverse modified to take
the new void* state argument.
2) disabled rpcclient: referring people to use SAMBA_TNG rpcclient.
i don't know how the other samba team members would react if i deleted
rpcclient from cvs main. damn, that code's so old, it's unreal.
20 rpcclient commands, instead of about 70 in SAMBA_TNG.
|
| | |
|
| |
| |
| |
| | |
changed it to "enum brl_type"
|
| |
| |
| |
| |
| | |
the last piece was to use a smb timeout slightly larger than the
locking timeout in bloking locks to prevent a race
|
| |
| |
| |
| |
| |
| |
| |
| | |
we now don't pass the lock type at all for unlocks.
I was surprised to discover that NT totally ignores the lock type in
unlocks. It unlocks a matching write lock if there is one, otherwise
it removes the first matching read lock.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
reply!
|
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
<jpjanosi@us.ibm.com>.
Jeremy.
|
| |
| |
| |
| |
| | |
hash is only useful when we fetch by key, not when we use
tdb_traverse()
|
| |
| |
| |
| | |
to using internal msrpc code in smbd.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I also fixed up the lookup_pdc_name() code so that it now works, even
with a NT server that insists on replying to udp/138.
The method I used to match packets was to use the mailslot string as a
datagram ID. The true dgm_id doesn't work as NT doesn't set it
correctly. uggh.
PS: Jeremy, I had to change your code quite a bit, are you sure this
worked with a Samba PDC?? The code looked broken, it got the offsets
wrong in the SMB portion of the packet and filled in the IP
incorrectly.
|
| | |
|