From: "Bostjan Skufca (at) domenca.com" <bostjan.skufca@domenca.com>
To: asterr <asterr@pobox.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: chroot of apache's cgi execution
Date: Mon, 19 Jan 2004 03:11:20 +0100 [thread overview]
Message-ID: <200401190311.20165.bostjan.skufca@domenca.com> (raw)
In-Reply-To: <Pine.BSF.4.21.0401171325300.89383-100000@hephaestus.sera.org>
could it be possible to redirect invocation of cgi scripts through some
"gateway" program which would setup chroot and execute perl and script
within?
On Saturday 17 of January 2004 05:27, asterr wrote:
> Only root is able to chroot. You would need to run apache as root or find
> a safe way to get root privileges for the chroot.
>
> On Sat, 17 Jan 2004, Bostjan Skufca (at) domenca.com wrote:
> > Hello all,
> >
> > can anybody give me some hint about chrooting execution of cgi script
> > invoked through apache?
> > I would like to achieve this on per-virtual-host basis so every virtual
> > host would have different root dir to which it would chroot execution of
> > it's cgi scripts. If the price is perl installation in every chroot jail
> > so be it.
> >
> > Best regards,
> >
> > Bostjan Skufca
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Best regards,
Bostjan Skufca
system administrator
next prev parent reply other threads:[~2004-01-19 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 3:45 chroot of apache's cgi execution Bostjan Skufca (at) domenca.com
2004-01-17 4:27 ` asterr
2004-01-19 2:11 ` Bostjan Skufca (at) domenca.com [this message]
2004-01-17 12:33 ` Joao Schim
2004-01-19 2:09 ` Bostjan Skufca (at) domenca.com
2004-01-19 9:45 ` Joao Schim
2004-01-19 14:02 ` Bostjan Skufca (at) domenca.com
2004-01-20 5:53 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401190311.20165.bostjan.skufca@domenca.com \
--to=bostjan.skufca@domenca.com \
--cc=asterr@pobox.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).