I think we should stay with the current configuration. A software such
as suphp cannot have common compile time options suitable for all
users:(
Default php4 cgi configuration doesn't set the user_dir and doc_root
options.
Many users are already using this debian packages and a change like this
o
> I don't think it's the best choice. Disable this is not a good idea
> for security reasons.
I disagree. A correctly configured php interpreter (meaning:
doc_root = "/var/www"
user_dir = "public_html"
in /etc/php4/cgi/php.ini) will perform the same check -- in the
sensible way: The script is ex
On Mar 3, 2005, at 6:59 AM, Emmanuel Lacour wrote:
On Wed, Mar 02, 2005 at 10:42:37PM -0800, [EMAIL PROTECTED] wrote:
One practical application of suPHP is to let each user run PHPs in
their UserDirs - with their permissions -
Unfortunately, the current configuration prevents this because
"~/public
On Wed, Mar 02, 2005 at 10:42:37PM -0800, [EMAIL PROTECTED] wrote:
> One practical application of suPHP is to let each user run PHPs in
> their UserDirs - with their permissions -
>
> Unfortunately, the current configuration prevents this because
> "~/public_html/" is probably not in DocumentRoo
Package: suphp
Version: 0.5.2-3
Severity: wishlist
One practical application of suPHP is to let each user run PHPs in
their UserDirs - with their permissions -
Unfortunately, the current configuration prevents this because
"~/public_html/" is probably not in DocumentRoot - leading to -
[...]
5 matches
Mail list logo
