Hey Daniel, Thanks for taking the time to help. For my application it looks like chroot'ed apache is all I need.
On Wed, Jan 26, 2011 at 3:59 PM, Daniel Llewellyn <[email protected]>wrote: > For a situation where you control the whole server and have only one > "client" (the client can be yourself or your company) which is allowed > access to all the web-served files then SuPHP will be meaningless. In > this scenario you would be transferring control from the apache user > (unprivileged) to another (also unprivileged) user, meaning a > redundant change of effective-userid. If I were deploying this > scenario then I would create a user account for the web data to be > served and set apache to impersonate that user itself, thereby > allowing me to utilise mod_php and technologies similar to the APC. > >
_______________________________________________ suPHP mailing list [email protected] https://lists.marsching.com/mailman/listinfo/suphp
