IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
('cvs ci filename' should be my friend:-)
get rid of some more global unconst vars.
I didn't find a referenz of this vars:
SIG_ATOMIC_T reload_after_sighup = 0;
SIG_ATOMIC_T got_sig_term = 0;
tridge: is it ok to remove them?
it compiles for me
metze
(This used to be commit b34a3104c63b36cec47acdedef36caaf571eb383)
- implement the interface_by_name() and interface_by_uuid() hooks
for the autogenerated dcerpc server boilerplates.
metze
(This used to be commit 0b6a291eb4b353259ad5b72f8731a5504d9dc8c7)
- fix the case when we have no fd_events left on the event_context
we now exit after doing the timed events and not block in select()
waiting for no fd's to become ready...
metze
(This used to be commit 857e76ef6b891c199534db6ce229410340286461)
handles are not shared between open dcerpc connections, even when
those connections are on the same SMB socket. I have tested this with
w2k3, w2k and NT4. It seems that policy handles have a strict scope of
the dcerpc connection on which they were opened.
I realise that this goes against existing folk-law in the team, but it
seems that the previous testing (I'm not sure who did this?) was
wrong. Perhaps clients do send us policy handles from other
connections, but if they do then the correct thing to do is to fail
the operation with a dcerpc fault. I suspect that failing it with
exactly the right dcerpc fault code is important.
(This used to be commit 2ed24d29bafd9055d5782acdd595cd0f378a651a)
common case of there being no pending partial data and a full dcerpc
packet being received.
We should use this same model for the smb server. It gives us
efficient memory usage while allowing for completely async socket
operations.
(This used to be commit 9aab321fb6e2f3499efd8ca5bc88ce2cb8e68219)
and let this be called by make [un]install
we can later change this and the make all
to not do the torture stuff, but for know only developers will
use samba4...
metze
(This used to be commit cb5f1e581fcb9eaf36926c3f341b0ab784031282)
and some stuff from configure.in and dynconfig.[ch]
make all
makes
bin/gentest bin/masktest bin/smbd
bin/locktest bin/smbclient bin/smbtorture
bin/ndrdump
now
metze
(This used to be commit e0043693a66a319ab7fef0e4202239c0b5d4bff8)
call it like:
script/find_unused_makefilevars.pl Makefile
or
script/find_unused_makefilevars.pl Makefile.in
metze
(This used to be commit ebecb6d05b97dc5bac8d9e48f8fad75dfbb44a74)
1.) We now register endpoint servers add startup via register_backend()
and later use the smb.conf 'dcerpc endpoint servers' parameter to setup the dcesrv_context
2.) each endpoint server can register at context creation time as much interfaces as it wants
(multiple interfaces on one endpoint are supported!)
(NOTE: there's a difference between 'endpoint server' and 'endpoint'!
for details look at rpc_server/dcesrv_server.h)
3.) one endpoint can have a security descriptor registered to it self
this will be checked in the future when a client wants to connect
to an smb pipe endpoint.
4.) we now have a 'remote' endpoint server, which works like the ntvfs_cifs module
it takes this options in the [globals] section:
dcerpc remote:interfaces = srvsvc, winreg, w32time, epmapper
dcerpc remote:binding = ...
dcerpc remote:user = ...
dcerpc remote:password = ...
5.) we currently have tree endpoint servers: epmapper, rpcecho and remote
the default for the 'dcerpc endpiont servers = epmapper, rpcecho'
for testing you can also do
dcerpc endpoint servers = rpcecho, remote, epmapper
dcerpc remote:interfaces = srvsvc, samr, netlogon
6,) please notice the the epmapper now only returns NO_ENTRIES
(but I think we'll find a solution for this too:-)
7.) also there're some other stuff left, but step by step :-)
This patch also includes updates for the
register_subsystem() , ntvfs_init(), and some other funtions
to check for duplicate subsystem registration
metze
(hmmm, my first large commit...I hope it works as supposed :-)
(This used to be commit 917e45dafd5be4c2cd90ff425b8d6f8403122349)
we needed to adjust the alignment of [relative] buffers for this to
work. I wonder if they are always 4 byte aligned?
(This used to be commit 9cd0a0b8b976e62c6da71b7e55cba5b38483620d)
