public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Kirkwood <markir@paradise.net.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: mod_suphp
Date: Thu, 21 Sep 2006 16:41:57 +1200	[thread overview]
Message-ID: <45121815.6030709@paradise.net.nz> (raw)
In-Reply-To: <1158810235.5996.20.camel@bullet.espersunited.com>

Michael Sullivan wrote:

>>
>> ;Path all scripts have to be in
>> docroot=/
>>
>> ; Security options
>> allow_file_group_writeable=false
>> allow_file_others_writeable=false
>> allow_directory_group_writeable=false
>> allow_directory_others_writeable=false
>>
>> ;Check wheter script is within DOCUMENT_ROOT
>> check_vhost_docroot=true
>>

> A little more information.  I have a file named test.php.  It's a simple
> print statement.  I have a copy in /var/www/localhost/htdocs/ and
> another one in /home/test/public_html/ .  The one
> at /var/www/localhost/htdocs/test.php works fine, but when I go to
> http://localhost/~test/test.php , I get this:
> 
> Internal Server Error
> File "/home/test/public_html/test.php" is not in document root of Vhost
> "/var/www/localhost/htdocs"
> 

I suspect that the directive 'check_vhost_docroot=true' is causing the 
error. I guess you need it set to false for what you want to work.... 
this lessens your security a bit unfortunately. I'm a little rust on Php 
configuration, but there should be some way to specify that *only* 
docroot and your userdir roots can execute php...

Cheers

Mark
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-09-21  4:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  3:34 [gentoo-user] mod_suphp Michael Sullivan
2006-09-21  3:43 ` [gentoo-user] mod_suphp Michael Sullivan
2006-09-21  4:41   ` Mark Kirkwood [this message]
2006-09-21  5:21     ` Michael Sullivan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45121815.6030709@paradise.net.nz \
    --to=markir@paradise.net.nz \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox