This might not be exactly what you're looking for, but here it is:
http://www.onlamp.com/pub/a/apache/2..._security.html
Basically put:
Quote:
Originally Posted by www.onlamp.com
If you have ever tried to chroot a web server you probably know that it is sometimes a complex task. With mod_security the complexity goes away. You are one configuration directive away from a chrooted server:
SecChrootPath /chroot/home/web/apache
The only requirement is that the web server path in the chroot be the same as the path outside of the chroot (in the example above, /home/web/apache). In addition to making chrooting very easy, this approach will allow you to have a chroot that contains only data files without binaries. This advantage comes from the fact that the chroot call is executed internally, after all the dynamic libraries are loaded and log files opened.
|
And if you're looking for a full chroot (note the above is an "internal chroot", which I read to mean the main apache process is NOT chrooted, but the spawned processes/threads ARE (correct me if I'm wrong, anyone)), then you might check out:
http://www.linux.com/article.pl?sid=04/05/24/1450203
It's not a CentOS specific guide, so you might need to tweak a few commands or settings...hope this helps...