Daniel J Walsh wrote: > On 12/02/2010 12:44 PM, Tony Molloy wrote: >> On Thursday 02 December 2010 17:37:54 m.roth@xxxxxxxxx wrote: >>> Tony Molloy wrote: >>>> On Thursday 02 December 2010 15:56:59 m.roth@xxxxxxxxx wrote: >>>>> Daniel J Walsh wrote: >>>>>> On 12/02/2010 09:35 AM, Tony Molloy wrote: >>>>>>> >>>>>>> I'm running http on a fully updated Centos 5 system. <snip> >>>>>>> I'm trying to run a cgi script from a user directory. >>>>> >>>>> <MVNCH> >>>>> >>>>>> Do you have httpd_suexec_disable_trans turned on? >>>>> >>>>> Actually, what bothers me is trying to run a .cgi from a user's >>>>> directory. Can't you create a directory ->under the apache >>> >>> <Directory><- that the >>> >>>>> users can put scripts in for testing? (I assume that once they're >>>>> good, they go into the real production location for .cgi.) >>>> >>>> Not so easily done ;-) >>>> >>>> This is a University environment with several hundred faculty/students >>>> wanting to use this server to run/check assignments. So they have ftp >>>> accounts where they can upload any scripts to their public_html directory and >>>> run them from there. >>> >>> I figured it was something like that. What I was thinking was >>> >>> /var/www/html/public_cgi/<students' directories> >>> which would put them in a *legitimate* place for apache to be happy >>> with, and which selinux would be happy with. >>> >>> You *might* need to add them to a group named something like pubcgi, >>> and make the above group acceptable to selinux and apache. >>> >> Interesting idea. I could give it a try next semester. > > It should not be necessary. public_html labeled correctly will work. > THe problem you are seeing is that this boolean was set causing suexec > to not work. You mean the group, Dan? I was thinking in terms of apache looking at ownership of files. Glad to know that the ownership, once it's in the correct place, isn't an selinux problem. mark -- selinux mailing list selinux@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/selinux