named pipe access

[Todd Pfaff]

On Fri, 22 Jan 1999, Luke Kenneth Casson Leighton wrote:

> > On Fri, 22 Jan 1999, Luke Kenneth Casson Leighton wrote:
> > 
> > > if you want named pipe, see IPC$ commands in smbclient.
> > 
> > do you mean see the source code in source/client/ that handles connections
> > to IPC$?  am i warm when i guess that i should be looking at
> > cli_call_api in clientutil.c and maybe look at the code in smbmount as an
> 
> clientutilARGH!  no, definitely not clientutil.c, although you're close:
> clientgen.c instead.  you will need to specify \PIPE\WHATEVERNAME not
> \PIPE\LANMAN.

ok, thanks for the pointer.  i'll stop bugging you now (for a few minutes
at least :-).

> my honest opinion is that you are probably better off writing dce/rpc
> functions instead of named pipe, i think you'll find that named pipe
> functions are a mess.
> 
> unless they are very clearly documented, do you have any examples?

yes, they are very well documented, but i don't have the documentation
handy right now.

the software documentation has an appendix that clearly describes all the
available name pipe API commands and the expected return strings.  the
documentation also states that "the rpc interface is for our
administrative clients and the published named pipe interface is for third
party developers".

i don't really follow how i would use the rpc interface.  would i have to
run an existing client that uses the rpc interface and deduce the rpc
functions from the netmon trace?  given the fact that i already have the
named pipe api well documented, this seems like a lot of work, and i don't
see the advantage.

--
Todd Pfaff                         \  Email: pfaff at mcmaster.ca
Computing and Information Services  \ Voice: (905) 525-9140 x22920
ABB 132                              \  FAX: (905) 528-3773
McMaster University                   \
Hamilton, Ontario, Canada  L8S 4M1     \