Re: [us...@httpd] Securing handler from direct access via URL. *RESOLUTION*

2010-09-10 Thread Daryl Tester
Jefferson Ogata wrote: On 2010-09-09 20:33, Daryl Tester wrote: This works as it should, but a side effect is that Action is exposing http:///cgi-bin/php5 to the outside world (which barfs when accessed directly). Access permissions on the cgi-bin directory appear to get propagated to the

Re: [us...@httpd] Securing handler from direct access via URL.

2010-09-09 Thread Daryl Tester
#x27;t recognize the potential threat. Opening sentence mentioned chroot'ing. I wrote was therefore not merely for your benefit, but for that of anyone who comes across this thread in the future. Fair enough. -- Regards, Daryl Tester "It's bad enough to have two heads, b

Re: [us...@httpd] Securing handler from direct access via URL.

2010-09-09 Thread Daryl Tester
tacker to submit input to them for interpretation. (Consider also POSTing to http:///cgi-bin/php5+/dev/fd/0.) Yes, again, I know it's dangerous, hence the concern of my original post. Was my subject line ambiguous? -- Regards, Daryl Tester "It's bad enough to have tw

[us...@httpd] Securing handler from direct access via URL.

2010-09-09 Thread Daryl Tester
7;m trying to "handle", so that doesn't help. Is there a way I can set up a handler but not have it directly exposed via URL (as opposed to the URLs it "handles")? Cheers. -- Regards, Daryl Tester "It's bad enough to have two heads, but it's worse when one