If your admins are going to get in a hyper-tiffy about what you're running, you have a couple of options:ĭo it in a VM (like I did for testing this answer).
#Can i install apache spark as root code#
Running Apache like a badass as My code above doesn't have an init script for it so you would need to replace or "fix" /etc/init.d/apache2 to stop a root-run version being run, and start your More than anything, the privilege-de-escalation model Apache has been using is battle tested. Sudo chown -R www-data: /var//apache2/Īnd there you are. sudo setcap 'cap_net_bind_service=+ep' /usr/sbin/apache2 At least not until you've read the whole post. Truth is you can break things to make this work. It just marshals unprivileged child processes. Some people talk about the initial root process as if it can be used to get privileges after startup. If you block www-data (or whatever user is running Apache) from reading config or certificates -which you can- you'll break the server. By default, the config can be read by any user. Or you can use iptables to redirect port 80 to an unprivileged port.
You can still bind low ports as non-root using the Linux capabilities framework (since 2.6.24) giving Apache the rights to bind to whatever ports it likes, regardless of user: sudo setcap 'cap_net_bind_service=+ep' /usr/sbin/apache2 Forget for a minute that you might want to run on an unprivileged port (some people do, I used to run Apache like this behind Nginx). I'll just address the things commonly cited as "definitely needing root" (above and elsewhere): All its scripts and configuration expect to use the root-then-drop-privileges model. That's not how it is by default though and it's that default behaviour that ships with Ubuntu that is making things really difficult for you.
It is possible to run Apache2 as something other than root. I disagree with the existing answer (and a hundred answers around the Internet).
0 kommentar(er)
