[SOLVED] [Adding users to apache group] Security risk ?
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The default permissions are usually 755 (umask 022) so apache can only read. And if an user is not a member of a group (apache in this case), he can not change the group of a file to that group (see btmiller's reply in this thread.
I don't want to give a sysadmin a call each time I have to change the group of a file or directory. That's why I want to add the users to the apache group.
Last edited by Wim Sturkenboom; 11-07-2007 at 10:22 PM.
I would make the directory world-writable (or writable to apache via acls, if you know anything about that one) and setgid the user (eg: chmod g+s directory). Then no changing groups is required (the files will be created owned by apache and group inherited from the directory). No adding users to the apache group is required, things are a little more sane, and the forward-facing fix is done in userspace.
Adding the user to the apache group is fairly safe, too.
I don't know anything about acls, so that option is off the menu for now.
I don't consider making the directory world-writable an option as anybody can write the directory in that case (something I'm trying to prevent).