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.
5.6.3. Daemon Accounts
Many daemons, such as Apache's httpd and MySQL's mysqld default to running as either "root" or "nobody". Running as "root" introduces obvious security problems, but the problems introduced by running everything as "nobody" may not be so obvious. Basically, if you're running every daemon as "nobody" and one of them gets comprimised, they all get comprimised. For this reason it is recommended that you create a user account for each daemon.
As reddazz said, 'nobody' is used by a number of different system processes for performing various activities, not just for running Apache with reduced privileges. In fact, it's actually not recommended to use 'nobody' as the Apache user for that very reason. Compromising the Apache service would give the attacker access to everything that that 'nobody' has access to, including other processes the are running under 'nobody'. It's a bit safer to use a dedicated user for Apache (many distros actually have a user named 'apache' for that purpose).
Distribution: slackware 12.0, Vector Linux STD 6.0 and 5.8, ZenWalk 4.6.1, OpenBSD 3.9
Posts: 389
Original Poster
Rep:
Quote:
Originally Posted by Capt_Caveman
As reddazz said, 'nobody' is used by a number of different system processes for performing various activities, not just for running Apache with reduced privileges. In fact, it's actually not recommended to use 'nobody' as the Apache user for that very reason. Compromising the Apache service would give the attacker access to everything that that 'nobody' has access to, including other processes the are running under 'nobody'. It's a bit safer to use a dedicated user for Apache (many distros actually have a user named 'apache' for that purpose).
i got ur point on creating a separate user for apache, (if that's the case, what should i do to "nobody" )
i got ur point on creating a separate user for apache, (if that's the case, what should i do to "nobody" )
Just leave it as it is because other daemons may need to use that account. All you need to do is create a user account for the apache user and configure apache to run as that user.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.