Description of the problem about the running permission of LinuxPhp:
The user who executes httpd is the httpd user group to which httpd belongs.
DocumentRoot:/webroot httpd drwxrwx ---
/Webroot/index.html httpd-r --------
/Webroot/index. php httpd-r --------
Index.html and index. php can be accessed normally.
In linux, does index. php require no execution permission?
Reply to discussion (solution)
In linux, does index. php require no execution permission?
Execution permission refers to a running process program. Similar to config, configure, make ......
For common .php).html files, you only need to have the read and write permissions. of course, some configuration files require the read and write permissions.
Integer permission refers to./command
Common web access is not implemented in this way, but parsed, so it is not required. If php is executed using./command, it is necessary.
Reply by referencing the author:
In linux, does index. php require no execution permission?
Execution permission refers to a running process program. Similar to config, configure, make ......
For common .php).html files, you only need to have the read and write permissions. of course, some configuration files require the read and write permissions.
During the secure deployment, should the execution permission of the writable directory be removed from the potential security risks?
In general, index. php is not required.
In the CGI mode of apache only, the STEP file must have executable permissions and specify the interpreter in the first line of the file.
It is not required in other modes. you only need to ensure that the files and directories are readable.