Doc #64559 [Opn]: Specify exactly what functions/statements the open_basedir directive affects

Edit report at https://bugs.php.net/bug.php?id=64559&edit=1 ID: 64559 Updated by: krakjoe@php.net Reported by: matteosistisette at gmail dot com Summary: Specify exactly what functions/statements the open_basedir directive affects Status: Open Type: Documentation Problem Package: Documentation problem PHP Version: Irrelevant Block user comment: N Private report: N New Comment: From a quick scan, dir, stat, link, file, fopen wrappers, temp files, glob and a bunch of extensions. I'm not sure of the terminology to use in the example, it should be the case that the author of any extension should be using open_basedir. Previous Comments: ------------------------------------------------------------------------ [2013-04-01 20:01:11] matteosistisette at gmail dot com Description: ------------ --- From manual page: http://www.php.net/manual/en/ini.core.php#ini.open-basedir --- --- open_basedir string Limit the files that can be opened by PHP to the specified directory-tree [...] When a script tries to open a file with, FOR EXAMPLE, fopen() or gzopen(), the location of the file is checked. --- FOR EXAMPLE?!?!?!?!?!?!?!? It is not clear whether or not this affects include, require, require_once and include_once. Please list all the file-opening functions and statements that this directive affects, or say "all except " and list those it doesn't affect. Or, if it affects all and every statement that may opens a file in any way, then state it clearly. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=64559&edit=1