RE: AW: AW: [cgiwrap-users] CGIWrap Error: Script dir not found

[Neulinger, N. <nn...@um...>]

CGIwrap does it the way it does, cause it was never designed to be used
with Action/etc. It was always set up for straight PATH_INFO based
execution.

In fact, cgiwrap long predates apache. I wrote it so that I could let
some untrusted users run cgi scripts on a small web server I ran on
A/UX. In fact, the original version didn't even let you use PATH_INFO,
you had to specify query string/get parameters to specify the user and
script.

Based on your syntax below, I'm sure you could trivially use mod_rewrite
to accomplish that support without a patch.=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nn...@um...
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Daniel Lorch [mailto:ml-...@lo...]=20
> Sent: Monday, August 05, 2002 7:43 AM
> To: Neulinger, Nathan
> Cc: dr...@gm...; cgi...@li...
> Subject: Re: AW: AW: [cgiwrap-users] CGIWrap Error: Script=20
> dir not found
>=20
>=20
> hi,
>=20
> > Seems like two two big ones are:
> >=20
> > 	No need for #!/usr/bin/php
> > 	No need for script to be executable
>=20
> Yup.
>=20
> > Anything else?
>=20
> What troubled me most was how CGIWRAP constructed the=20
> cgiBaseDir. It might
> increase security, but it didn't work with our setup:
>=20
>   /home/<user>/public_html/<subdomain>/
>=20
> That's the main reason I had to patch CGIWRAP myself. Why=20
> isn't PATH_TRANSLATED
> used instead? Are there any security concerns?
>=20
> -daniel
>=20