summaryrefslogtreecommitdiff
path: root/source3/rpc_client/rpc_transport_smbd.c
AgeCommit message (Collapse)AuthorFilesLines
2009-02-02Next step disentangling async_req from NTSTATUSVolker Lendecke1-2/+2
Now I need to document this :-)
2009-02-01Split up async_req into a generic and a NTSTATUS specific partVolker Lendecke1-15/+15
2009-01-30Add the "SMBD" rpc transportVolker Lendecke1-0/+694
The idea of this is that all client utils like smbpasswd and also for example "net join" do not access our internal databases like passdb and secrets.tdb directly anymore but pass everything throught the well-established RPC interfaces. The way you use this is the following: With rpc_cli_smbd_conn_init() or its async variant you initialize a "struct rpc_cli_smbd_conn". This structure is the link to a freshly forked smbd, ready to be used for RPC services. You should only ever have one such structure in your program. More don't hurt, but are plainly unnecessary. If you want to use the SAMR pipe to change a passwort, you connect to that pipe with rpc_pipe_open_local. Do you normal rpccli_samr calls on that and your locally forked smbd will connect to passdb for you. GD, this might make the distinction between the _l and _r calls in libnetapi mostly unnecessary. At least it is intended to do so... :-)