outsourcing DCE/RPC to alternate programs - runtime config option

[Jelmer Vernooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Luke Kenneth Casson Leighton wrote:
| On Sun, Dec 12, 2004 at 10:12:31AM +1100, tridge at samba.org wrote:
|
|>Michael,
|>
|> > Forgive my ignorance, but:  If one wants the DCE RPC functionality
only, can
|> > they use the Samba RPC?
|>
|>In Samba4 you would do this:
|>
|>	server services = rpc
|>
|>and this would make Samba only start the rpc server (so it would not
|>start the builtin smb or ldap servers). It will only be listening on
|>tcp ports 135 and 1024, plus any local rpc transports that are defined
|>(such as /var/ncalrpc/DEFAULT and /var/ncalrpc/EPMAPPER) and any fixed
|>ncacn_ip_tcp ports defined in the builtin IDL files.
|
|
|  tridge - please excuse me for mentioning this but after
|  _everything_ you said that i wasn't "allowed" to do because
|  of various detailed technical descriptions, NOW you add in a
|  ncalrpc transport into samba 4 and because it's you adding it,
|  it's suddenly acceptable??
|
|  ... did i miss something?

I think what Tridge means is actually 'forwarding' the RPC data (for
which Samba4 already has support, e.g. you can redirect a complete pipe
to a remote server) instead of having a hack that bypasses the local
endpoint and talks to a local pipe.

|  i assume the samba 4 ncalrpc implementation is root-only-accessible, yes?
Yes, at the moment.

|  or, did you find a solution to opening /var/ncalrpc/ local transports
|  as ordinary users?
We haven't looked at that yet though we will need to in the future -
I've been working on some GUI utilities that need to talk to the local
smbd somehow - ncalrpc would fit in perfectly here.

Cheers,

Jelmer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBu4vYPa9Uoh7vUnYRAk5XAJ9owsvg5xfqLctT5wkpyuz915SJcQCeMB9P
1sRzCYFR38wmhF3AIFC9Mts=
=H4ql
-----END PGP SIGNATURE-----