samba run-time modification to smb.conf files

[Christopher R. Hertel]

Jeremy,

As a *long term* goal, I'm suggesting that we provide a managment and
query connection (I'm in favor of something that is *only* available from
the local host).  The connection would provide read and (secure) write
access to/from internal databases.  Such a connection doesn't need to be
complex.  It should, in fact, be simple, straight-forward, solid, and
fast. 

Such a connection would allow us or third parties to write things like
LDAP or SQL back-ends, or provide an interface to Oracle, Sybase, WWW CGI,
etc.  I'd also like to see a command-line tool.

I agree that we're not ready for code.  We need a design, first.  Then we 
need to gently move the existing system in the right direction.

How smb.conf fits into all this is only one (small) issue.

Chris -)-----

> Luke Kenneth Casson Leighton wrote:
> > 
> > there are numerous dce/rpc "set" calls.  is it reasonable to support
> > these?
> > 
> > if so, we will need to add the capability (currently only found in swat)
> > to smbd to write to smb.conf files.  this is one reason why i suggested
> > that swat (or swat v2) go "via" a samba daemon instead of editing smb.conf
> > files direct.
> > 
> 
> Hmmmmmm. Can we think about this and not rush in with
> code yet.
> 
> Writing to smb.conf is a security *nightmare* :-).
> 
> Also our remote admin is *much* better than NT
> (telnetd ships as standard with all UNIXs :-) so
> we may not need this right now.
> 
> Cheers,
> 
> 	Jeremy.
> 
> -- 
> --------------------------------------------------------
> Buying an operating system without source is like buying
> a self-assembly Space Shuttle with no instructions.
> --------------------------------------------------------
> 


-- 
Christopher R. Hertel -)-----                   University of Minnesota
crh at nts.umn.edu              Networking and Telecommunications Services