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

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

I have applied most of Piotr's patch with changes...

I have not enabled part of it though - which is the part messing with
PATH_INFO, cause I'm not quite sure of why that is being done.

If you're a php-cgiwrap user, you might check out and build the latest
cgiwrap, and let me know if it works ok for you. If you have any info on
the PATH_INFO handling, speak up.=20

Also, since I'll likely release this as 3.8, are there any other fixes
to PATH_INFO, PATH_TRANSLATED, etc. That should be applied? If someone
can describe what is wrong now, and point me at details as to how it
should behave, I'll fix for 3.8.=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