Detailed explanation of php open_basedir security and usage_PHP tutorial

The function of open_basedir is to specify the directory location, which means to limit the files that PHP can open to the specified directory tree, including the file itself, and is not affected by whether it is in safe mode or not.

The following is the original description and default configuration in php.ini:
; open_basedir, if set, limits all file operations to the defined directory
; and below. This directive makes most sense if used in a per-directory or
; per-virtualhost web server configuration file. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
open_basedir = .
open_basedir can limit the user's activity scope of accessing files to a specified area, usually the path of their home directory, also
The symbol "." can be used to represent the current directory. Note that the restrictions specified with open_basedir are actually prefixes, not directory names.
For example: if "open_basedir = /dir/user", then the directories "/dir/user" and "/dir/user1" are both
accessible. So if you want to restrict access to only a specified directory, end the pathname with a slash. For example, set it to:
"open_basedir = /dir/user/"

open_basedir can also set up multiple directories at the same time. Use semicolons to separate directories in Windows and
in any other system. Colon separated directories. When it acts on the Apache module, the open_basedir path in the parent directory is automatically inherited.

There are three ways to make independent settings for specified users in Apache:

(a) The corresponding setting method of Directory in Apache’s httpd.conf:

php_admin_value open_basedir /usr/local/apache/htdocs/
#To set multiple directories, please refer to the following:
php_admin_value open_basedir /usr/local/apache/htdocs/:/tmp/

(b) The corresponding setting method of VirtualHost in Apache’s httpd.conf:
php_admin_value open_basedir /usr/local/apache/htdocs/
#To set multiple directories, please refer to the following:
php_admin_value open_basedir /var/www/html/:/var/tmp/

(c) Because after open_basedir is set in VirtualHost, this virtual user will no longer automatically inherit php.ini
The value of open_basedir in VirtualHost
is not set, which makes it difficult to achieve flexible configuration measures. Set this restriction in php.ini. For example, you can set open_basedir = .:/tmp/ in php.ini. This setting means that it is allowed
Access the current directory (that is, the directory where the PHP script file is located) and the /tmp/ directory.

Please note: If the temporary directory for uploading files set in php.ini is /tmp/, then you must
when setting open_basedir Include /tmp/, otherwise the upload will fail. The new version of php will prompt "open_basedir restriction in effect"
Warning message, but the move_uploaded_file() function can still successfully remove the uploaded file in the /tmp/ directory, I don’t know
Is this a bug or a new feature.

http://www.bkjia.com/PHPjc/632827.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/632827.htmlTechArticleThe function of open_basedir is to specify the directory location, which means to limit the files that PHP can open to the specified directory tree , including the file itself, and is not affected by whether it is in safe mode or not. ...