[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Handling the new Apache chroot
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: Re: Handling the new Apache chroot
- From: "C. Bensend" <benny_(_at_)_bennyvision_(_dot_)_com>
- Date: Wed, 6 Nov 2002 17:54:01 -0600
- Mail-followup-to: ports_(_at_)_openbsd_(_dot_)_org
On Thu, Nov 07, 2002 at 12:15:20AM +0100, Henning Brauer wrote:
> however, sometimes you have not much choices. not beeing libc-specific - of
> course a merely empty chroot is best. but if you need to run application/cgi
> X, it is still better to have the stuff app X needs inside the chroot than
> running -u just because it works then.
I totally agree, Henning... In this specific instance, I do
have an alternative, and it's one that keeps libc out of the
Your second point is a good one too - it _would_ be better
to copy libwhatever into the chroot and continue using the
chroot, rather than eliminate it altogether.
Thanks for all your help/discussion!
There's always time for Cheerios...