A big river

How to determine whether the Linux server is invaded?

 How to determine whether the Linux server is invaded?
In this guide, the so-called server has been invaded or hacked means that unauthorized people or programs log in to the server for their own purposes and use its computing resources, which usually has a bad impact. Disclaimer: If your server is invaded by a state organ like NSA or a criminal group, you will not notice any problems, and these technologies cannot detect their existence. However, most of the compromised servers are intruded by programs like automatic attack programs or cheap attackers like "script kids", as well as stupid criminals. Such attackers will abuse server resources while accessing the server, and seldom take measures to hide what they are doing
Read on

Centos prohibits IP connections to SSH services

1. Modify the/etc/hosts. deny file. The command is as follows: sudovi/etc/hosts. deny 2. Rules for writing content: # Deny specifying IPsshd: 127.0.0.1 # Deny IP segment (wildcard symbol '.') sshd: 127.0.0
Read on

Linux counts the frequent IP accesses of nginx through the awk command

The command is as follows: tail-10000/nginx_log_path. log | awk vFS='|' '{print $2}' | sort | uniq-c | sort-k1-nr | head-n20
Read on

Server firewall URL white list rule settings

 Server firewall URL white list rule settings
The Z-BLOG plug-in provided by this website needs to be automatically processed through regular access to specific URLs, but some friend servers are equipped with firewalls, which leads to the URL triggering the plug-in execution being intercepted by mistake. Friends who do not know the technology will panic at this time. In fact, there is no need to panic. We can configure the URL white list in the firewall to solve the problem
Read on

Update server DNS settings with pagoda "Linux toolbox"

 Update server DNS settings with pagoda "Linux toolbox"
The reason for writing this tutorial is that I recently moved a home for the website domain name. Because I reset the DNS server and resolution of the domain name, users in some regions who did not refresh DNS in time could not access my website. For the latest resolution, the DNS cache time (TTL) I set is one hour, but some users have not been updated in time due to the server cache. In this case, you can manually update the server DNS settings to make them take effect. In view of the pagoda panel used by most webmaster friends, this tutorial takes pagoda as an example. Note: It is not necessary to update manually. When the server cache time is up, it will be automatically updated. This depends on the server cache time
Read on
search
«     April 2024     »
one two three four five six day
one two three four five six seven
eight nine ten eleven twelve thirteen fourteen
fifteen sixteen seventeen eighteen nineteen twenty twenty-one
twenty-two twenty-three twenty-four twenty-five twenty-six twenty-seven twenty-eight
twenty-nine thirty
Recent messages
Site Label
Farmers