Re: [webmin-l] Webmin Doesn't Clean ENV

[Jamie C. <jca...@we...>]

On 26/May/2006 16:13 Agustin Pizarro wrote ..
> On Friday 26 May 2006 20:48, Jamie Cameron wrote:
> > On 26/May/2006 12:15 Agustin Pizarro wrote ..
> >
> > > Hi All,
> > >
> > > I have been searching the web  because I have that problem (see subject)
> > > with
> > > version 1.260
> > >
> > > Even if this http://seclists.org/lists/bugtraq/2001/May/0258.html says
> > > it has
> > > been fixed on 0.83 when I restart my Apache server I can see webmin
> SID
> > > with
> > > PHP phpinfo() function which may be a serious security problem as it
> says
> > > here: http://seclists.org/lists/bugtraq/2001/May/0275.html
> > >
> > > Has this been fixed?
> > >
> > > How do I get ENV cleaned when restarting Apache with webmin?
> > >
> > > I am using the miniserv.pl server.
> >
> > Does this still happen if you stop and re-start Apache from within
> > Webmin? I am pretty sure this problem is fixed by clearing all environment
> > variables before calling Apache, although if you just do a restart or
> apply
> > changes Apache may still be inheriting variables from a previous incorrect
> > version of Webmin.
> >
> > Also, are you using Virtualmin there? It has its own slightly different
> > Apache restart code.
> >
> >  - Jamie
> 
> No, I am not using Virtualmin.
> I have tried what you suggest and it happens only on "Apply Changes" when
> direct restart command is executed within webmin (in my case 
> '/etc/rc.d/init.d/httpd restart').
> 
> stop, start -> ok, clean (*)
> stop, start, apply(start-stop) -> ok, clean (*)
> stop, start, apply(apachectl) -> ok, clean (*)
> stop, start, apply(command) -> not clean
> 
> So setting on the module config "Command to apply configuration" to "Run
> stop 
> and start commands" or "Use apachectl or HUP signal" solves the problem
> 
> (*) Clean mostly as :
> 
> _ENV["SERVER_REALROOT"]	/usr/libexec/webmin
> _ENV["PWD"]	/usr/libexec/webmin/apache/
> 
> keep set.
> 
> Thanks
> 
> Thank you very much too for giving us this useful tool and your support.

Ok, that makes sense now .. you are seeing a bug that existed in Webmin 1.260,
but has been fixed in the 1.270.

 - Jamie