Although I'm not convinced "System and Network Config" is the correct forum for this, the historical posts related to Apache HTTP tend to cluster here.
OK. It's been years since I futzed with web servers, but I want to do some home automation stuff: tomcat, apache2, CGI, etc.
For security reasons I firmly believe that all name based virtual hosts should exist under their own UIDs, or at least distinct GIDs. Problem is that apache2 seems broken with regard to distinct UID/GID in the VirtualHost declarations. and yes, I'm aware of mpm_itk and mpm_prefork. The near nonexistent online discussions about mpm_itk make me think noone is using it, but the sparse docs do say that to run virtual hosts in their own user context that is the way to go.
Now here's the clencher: for the virtualhost httpd server processes to run under the chosen UIDs, the main apachectl would need to start the parent server as root, and it seems somebody upstream decided that is a bad idea and disabled the running of apache2 under root, at least in Debian. Hmmm...
Thoughts?
OK. It's been years since I futzed with web servers, but I want to do some home automation stuff: tomcat, apache2, CGI, etc.
For security reasons I firmly believe that all name based virtual hosts should exist under their own UIDs, or at least distinct GIDs. Problem is that apache2 seems broken with regard to distinct UID/GID in the VirtualHost declarations. and yes, I'm aware of mpm_itk and mpm_prefork. The near nonexistent online discussions about mpm_itk make me think noone is using it, but the sparse docs do say that to run virtual hosts in their own user context that is the way to go.
Now here's the clencher: for the virtualhost httpd server processes to run under the chosen UIDs, the main apachectl would need to start the parent server as root, and it seems somebody upstream decided that is a bad idea and disabled the running of apache2 under root, at least in Debian. Hmmm...
Thoughts?
Statistics: Posted by kent_dorfman766 — 2024-12-17 03:50 — Replies 0 — Views 24