Three methods to defend against PHP Trojan attacks

This article introduces some techniques to defend against PHP Trojan attacks. through these techniques, you can better prevent Trojans. 1. avoid jumping out of the Web Directory and first modify httpd. conf. if you only allow your php script program to operate in the web directory, you can also modify the httpd. conf file to limit the php operation path. For example, your web directory is/usr/local/apac. This article introduces some techniques to defend against PHP Trojan attacks. through these techniques, you can better prevent Trojans.

1. prevent jumping out of the Web Directory
First, modify httpd. conf. if you only allow your php script program to operate in the web directory, you can also modify the httpd. conf file to limit the php operation path. For example, if your web directory is/usr/local/apache/htdocs, add the following lines in httpd. conf:

Php_admin_value open_basedir/usr/local/apache/htdocs
In this way, files other than/usr/local/apache/htdocs to be read by the script will not be allowed. if the error is displayed, the following error will be prompted:
Warning: open_basedir restriction in effect. File is in wrong directory in/usr/local/apache/htdocs/open. php on line 4
And so on.

2. prevent php Trojans from executing webshell
Enable safe_mode and set it in php. ini.
Disable_functions = passthru, exec, shell_exec, system
Select either of them.

3. prevent php Trojans from reading and writing file directories
Disable_functions = passthru, exec, shell_exec, system in php. ini
Add the php file processing function.
Mainly include
Fopen, mkdir, rmdir, chmod, unlink, dir
Fopen, fread, fclose, fwrite, file_exists
Closedir, is_dir, readdir. opendir
Fileperms. copy, unlink, delfile

Become
Disable_functions = passthru, exec, shell_exec, system, fopen, mkdir, rmdir, chmod, unlink, dir
, Fopen, fread, fclose, fwrite, file_exists
, Closedir, is_dir, readdir. opendir
, Fileperms. copy, unlink, delfile

Okay, it's done. we have no choice but to use the php Trojan. Unfortunately, those things that use the text database won't work anymore.

If apache is built on the windos platform, we still need to note that apache runs the system permission by default, which is terrible, which makes people feel uncomfortable. let's drop apache permissions.
Net user apache fuckmicrosoft/add
Net localgroup users apache/del
OK. We have created a user apche that does not belong to any group.

Open the computer manager, select a service, click the apache service attribute, select log on, select this account, fill in the account and password created above, restart the apache service, OK, apache runs under low permissions.

In fact, we can also set the permissions for each folder so that apache users can only execute what we want it to do, and create a single read/write user for each directory. This is also a popular configuration method for many VM providers. However, this method is used to prevent minor usage.