mirror of
https://github.com/samba-team/samba.git
synced 2024-12-29 11:21:54 +03:00
af237084ec
event_context for the socket_connect() call, so that when things that
use dcerpc are running alongside anything else it doesn't block the
whole process during a connect.
Then of course I needed to change any code that created a dcerpc
connection (such as the auth code) to also take an event context, and
anything that called that and so on .... thus the size of the patch.
There were 3 places where I punted:
- abartlet wanted me to add a gensec_set_event_context() call
instead of adding it to the gensec init calls. Andrew, my
apologies for not doing this. I didn't do it as adding a new
parameter allowed me to catch all the callers with the
compiler. Now that its done, we could go back and use
gensec_set_event_context()
- the ejs code calls auth initialisation, which means it should pass
in the event context from the web server. I punted on that. Needs fixing.
- I used a NULL event context in dcom_get_pipe(). This is equivalent
to what we did already, but should be fixed to use a callers event
context. Jelmer, can you think of a clean way to do that?
I also cleaned up a couple of things:
- libnet_context_destroy() makes no sense. I removed it.
- removed some unused vars in various places
(This used to be commit
|
||
---|---|---|
.. | ||
common | ||
man | ||
tools | ||
config.m4 | ||
config.mk | ||
README | ||
reg_backend_dir.c | ||
reg_backend_gconf.c | ||
reg_backend_ldb.c | ||
reg_backend_nt4.c | ||
reg_backend_rpc.c | ||
reg_backend_w95.c | ||
reg_backend_wine.c | ||
reg_samba.c | ||
TODO | ||
winregistry.pc.in |
This is the registry library. The registry is basically a bunch of hives that can be loaded from different places. The various registry backends provide support for loading/saving specific types of hives: - ldb - w95 (USER.DAT-style files) - nt4 (NTUSER.DAT-style files) - gconf (GNOME configuration) - rpc (Remote individual hives) Instead of opening individual hives, one can also open a 'complete' registry by using one of these three functions: - reg_open_local() - load local registry, see below - reg_open_remote() - connect to remote registry over RPC - reg_open_wine() (not working yet) reg_open_local() loads a set of hives based on smb.conf settings. Lines in smb.conf should have the following syntax: registry:<hivename> = <backend>:<location> So an example usage could be: registry:HKEY_CURRENT_USER = nt4:NTUSER.DAT registry:HKEY_LOCAL_MACHINE = ldb:tdb://registry.tdb WERR_NOT_SUPPORTED will be returned for all hives that haven't been set. On Windows the various registry hives are loaded from: HKEY_CURRENT_CONFIG: %SystemRoot%\System32\Config\System HKEY_CURRENT_USER: %Profile%\NTUser.dat HKEY_LOCAL_MACHINE\SAM: %SystemRoot%\System32\Config\Sam HKEY_LOCAL_MACHINE\Security: %SystemRoot%\System32\Config\Security HKEY_LOCAL_MACHINE\Software: %SystemRoot%\System32\Config\Software HKEY_LOCAL_MACHINE\System: %SystemRoot%\System32\Config\System HKEY_USERS\.DEFAULT: %SystemRoot%\System32\Config\Default HKEY_LOCAL_MACHINE\HARDWARE: is autogenerated