Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am running Audio Galaxy ( connected to the internet all the time ) as a daemon in the background.
Now I heard that you can run it as a special user ( with no rights ).
But how?
You could use the user 'nobody', but to Apache the user nobody is somebody. The nobody user would have rights to whatever files he owned.
I'd suggest that you create a new user called 'agalaxy' (or whatever) and make him non-login able and dedicated to this application ONLY. Set the ownership of the directory and all the Audio Galaxy files to this user, and launch the program as this user.
Apache didn't invent the user, it's a standard trust no-one over networks logging name from the BSD days.
If Apache is run correctly the daemon runs as user nobody but the files it runs should be owned by someother user like "webadmin" and group "webstuff" then all the files should have the privileges set with chmod 644.
This way if a bug lets someone run files with the id of the httpd your not going to get very far.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.