note 110788 deleted from ini.core by danbrown
| From: | danbrown@php.net | Date: | Fri, 07 Dec 2012 18:01:08 +0000 |
| Subject: | note 110788 deleted from ini.core by danbrown | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-192392@lists.php.net to get a copy of this message | ||
Note Submitter: bee kay two at me dot com
----
disable_functions appears to give no diagnostic when it fails. Nothing shows up in error log. In
contrast, violation of open_basedir shows a clear error message. Very confusing.
On another note, for security i have most File functions disabled, but would like to open it up
enough to allow a blog php package to function. There appears to be no way to identify which
functions are being called (which I would expect to show up in an error log.) Is there?
Is there a way to "open" up the permissions in a given folder, via .htaccess for example?
Can .htaccess set a new "system" php.ini to be active for a specific folder tree?
consider website.com, and website.com/blog. How would one
set a tighter open_basedir and looser disable_function in website.com/blog?