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.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Because one of the few services on Linux open to random connections is Apache and there are many Apache modules, particularly mod_php that have abysmal security records. If you run Apache chrooted and it gets compromised, the attacker cannot do anything outside the chroot. This means that they can possibly mess with your website, but not do any damage to the rest of your system.
Note that for this to work correct, Apache cannot be run as root, it must be run as some unprivileged user. Also, none of the files in the chroot area should be writable by this user that's running Apache, that way an attacker who manages to exploit Apache hopefully won't even be able to modify your website files! This is a very nice degree of security, certainly much, much better than running Apache as root and letting it access the entire system.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Well, that's a concious decision and those directories would be subject to damage if Apache is ever compromised. Better keep up to date with security patches!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.