On 16.06.09 17:11, Igor Cicimov wrote:
> Running apache in chroot adds another layer of security. You can chroot the
> apache server and copy over all the libraries you need and only the programs
> you need like /bin/sh lets say to start/stop the server. In that way any
> security issue or intruder
Hi Igor.
chroot, like Fred said, add another security layer in your environment,
protecting the OS from the Web Server. I mean, if web server have be
compromised, the person will have access just to the web server.
chroot is a good option to secure your webserver, but maybe it's not easily
to bui
Running apache in chroot adds another layer of security. You can chroot the
apache server and copy over all the libraries you need and only the programs
you need like /bin/sh lets say to start/stop the server. In that way any
security issue or intruder will end up in "jail" and have limited program
Hello everyone
I can't seem to get my head around this chrooted and non-chrooted apache
server thing at all.
What are the pros & cons, advantages or dissadvantages of chrooted over
non-chrooted apache servers.
In a nutshell, is a preferable to run apache chrooted on a production
server or not?
