On Fri, 15 Sep 1995 long-morrow @
> It can be a pain (you have to make sure that anything that CGI programs needs --
> shared libraries, perl interpreter and library modules -- exists within the
> chroot()d hierarchy, but it should help to contain a CGI program gone haywire
> (or one that an external WWW user attempted to trick and hijack).
> We run a number of CGI programs in a chroot()d environment.
> - Morrow
Would you mind sharing what you needed to move to the chrooted
environment to make CGI work??
========= << raj >> == http://www.brainlink.com/~frostbit/ ==============
SYADMIN: BrainLINK System (718) 805-8868 // http://www.brainlink.com
GCS d++ H-- s+:+ !g p2 !au a- w+ v-* C++++ US++++ L++ P+++ E- N+ W---
M-- po Y+ t-- 5+++ j++ tv b+++ e++ u+ h++ f+ r++ n+ y+