What chroot() is really for
Posted Oct 7, 2007 17:56 UTC (Sun) by thedevil
In reply to: What chroot() is really for
Parent article: What chroot() is really for
>> The apache example is a good one. One should always have several layers of security, and putting apache in a chroot is such a layer - and a good one at that. The "risk" of someone finding a bug in some website software is VERY high - even if it's your own software and you've been security conscious - we all make mistakes, and also new bugs is found in PHP and other languages all the time. <<
How do you enable per-user web directories (typically ~/public_html) if the webserver is chrooted?
to post comments)