I'm glad you find it useful. Please let me finish it since I have seen that it fails sometimes.
The patch I submitted would do the trick *if* there was a global user. In the next version I submit, though, I'll add the option you are looking for. On Fri, Jun 11, 2010 at 5:42 PM, Elliott Forney <[email protected]> wrote: > This looks like great work. However, I am still concerned that this > will not solve our problem. It is typical for us to have a project > directory that is owned by the project leader (we are in a university > setting so in our case this would be a professor) and to have a number > of people (in our case students) adding php scripts to the project > directory. Each project has it's own UNIX group but there is not a > common user. Ideally, we would like to have an option to simply > disable the parent directory check in the suphp config file. We are > willing to trust that the owners of the directory will not trash the > scripts it contains. In fact, we would like for them to be able to. > > Thanks! > Elliott Forney > > On Fri, Jun 11, 2010 at 2:00 PM, corrideat <[email protected]> wrote: >> I've written a patch for suPHP that enables this three new things: >> >> . Support for common space (-DCOMMON_POOL): Means that you can run >> scripts owned by, e.g., user "hosting" as another user. This user is >> considered "safe" >> >> . Support for execution support: Means that in addition to >> "execute:!self", you can set e.g. "execute:/usr/bin/mono". This way >> you can set interpreters for non-PHP CGIs. >> >> . Directory can now be owned by the common user. >> >> I hope this gets merged into the main truck soon. Consider this patch >> file to be under the MIT license (which is itself GPL-compatible). >> >> >> >> On Fri, Jun 11, 2010 at 4:00 PM, Elliott Forney <[email protected]> >> wrote: >>> Hi All, >>> >>> We recently began using suphp on our shared hosting environment and >>> are generally quite happy with the results. However, the fact that >>> suphp checks parent directory ownership has been a problem for some of >>> our sites in shared project directories. Our current solution is to >>> simply recompile the source with this check commented out, lines >>> 550-556 in Application.cpp. I see that others have written the code >>> necessary to make this an option in the suphp.conf >>> http://www.mail-archive.com/[email protected]/msg00762.html >>> My question is: is there any chance of this making it into the next >>> release of suphp? It would be nice to have this in the official >>> package instead of having to recompile with each release. >>> >>> Thanks, >>> Elliott Forney >>> >>> _______________________________________________ >>> suPHP mailing list >>> [email protected] >>> https://lists.marsching.com/mailman/listinfo/suphp >>> >> >> >> >> -- >> Ricardo I. Vieitez >> Estudiante secundario >> [email protected] >> Página web personal: msl37.org >> Bitácora: blog.msl37.org >> > -- Ricardo I. Vieitez Estudiante secundario [email protected] Página web personal: msl37.org Bitácora: blog.msl37.org _______________________________________________ suPHP mailing list [email protected] https://lists.marsching.com/mailman/listinfo/suphp
