You are not logged in.
Pages: 1
Hi,
I'm still learning Linux, and I'm wondering what is the generally recommended way to handle permissions on an Archlinux server? For example, I often use the /etc/rc.d scripts to start/stop/restart various daemons. I normally do it like so:
sudo /etc/rc.d/httpd restart
However, I wanted to be able to do this through normal means, if necessary. I have my own user when I administrate my server, I do not login as root. This user really can't do much of anything I find, except for things already in my home directory. When it comes to executing scripts, I always find myself running most commands with root privileges. Am I approaching this in an acceptable way? If not, could someone describe the better "general practice" to follow? Thanks.
Offline
Well, I would say that you definitely want to have to have root access for all the /etc/rc.d/ scripts on a server. The trick is to make sure root access is hard to come by. For example, if the server has ssh access, making sure that you can't ssh in as root.
Offline
Either using sudo or some sort of RBAC system is recommended. A lot better than su-ing into root since you can limit abilities and it logs the actions.
Offline
Pages: 1