dce/rpc "client" api

[Luke Kenneth Casson Leighton]

On Fri, 18 Aug 2000, Gerald Carter wrote:

> Luke Kenneth Casson Leighton wrote:
> > 
> > to disable ncaclrpc, it will then be a matter of 
> > commenting out 3 lines of code.
> > 
> > andrew proposed making it an lp_xxx configureable item.
> 
> Ummm...this would be fine for a default transport.
> But would avouid being able to specify it on a per 
> connection basis (whicih is of course the most 
> flexible).

i don't quite follow you.

andrew would like it to be an smb.conf option because he would like a
justification for the existence of the ncalrpc loop-back transport, given
that "ncacn_np over SMB over 127.0.0.1 _should_ be sufficient".
 
> ...and just to clarify, we are talking about client side
> code here for the immediate.

yes.

>  I realize this applies to server code as well, but I don't think we
> are talking about doing that just yet are we?

no... well...

in TNG, the default transport for DCE/RPC _is_ ncalrpc.  anything else
[whether SMB or TCP] *redirects* to ncalrpc.

so smbd is purely a redirector.  there *is* no server-side DCE/RPC code in
smbd *whatsoever*.

i intend to write a... a... [think-of-a-name,quick!] dcetcpd "thing" which
will be incredibly simple.  it will listen on a TCP port, it will send an
"anonymous credentials setup" over ncalrpc, and from then on it will
simply read_data() followed by write_data() and vice-versa to communicate
between the TCP socket and the unix domain socket.

i reckon this could be done in about... 300 lines of code! :)