Article Title: Ten mistakes that Linux administrators can easily make. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.
Migration to Linux is a pleasure for many people. For others, this is a nightmare. Especially for some administrators who have just entered the Linux management gate, if some common errors are not avoided, it is easy to bring security risks to the network or system of the Organization. This article provides some suggestions to help these beginners avoid these errors.
Error 1: download and install various types of applications from multiple channels without strict review
At first glance, this may be a good idea. If you are running Ubuntu, you will know that the package management program uses the. deb software package. However, many applications you find are provided in the form of source code. No problem? These programs may work properly after installation. But why can't you install programs at will? The principle is simple. If you install a program as a source, your software package management system will not be able to track what you have installed. Therefore, Package A (installed as A source) depends on Package B (from. the deb library is installed), and when Package B is updated from the update manager, what will happen? Package A may or may not run. However, if both Package A and Package B are installed from the. deb library, the chances of both packages running will be higher. In addition, it is easier to update a package when all packages come from the same binary type.
Error 2: Ignore updates
This does not mean that Linux administrators lack skills. However, after running Linux, many Linux administrators think there will be nothing to do in the future and think it is safe and reliable. In fact, new updates can patch some new vulnerabilities. Maintaining updates builds a watershed between a vulnerable system and a secure system. Linux security comes from constant maintenance. To achieve security, any administrator should keep up with the Linux updates to use new features and stability.
Error 3: Bad Password
Remember, the root password is usually critical to the linux kingdom. So why is the root password so easy to crack? It is essential to ensure the robustness of your user passwords. If your password is long and hard to remember, you can store it in an encrypted location. You can use the decryption software to unlock the password when you need it.
Error 4: Start the server to X
When a machine is a dedicated server, you may want to install X, so that some management tasks will be simpler. However, this does not mean that the user needs to start the server into X. This will waste precious memory and CPU resources. On the contrary, you should stop the Startup Process on level 3 and enter the command line mode. This will not only leave all resources to the server, but also prevent the leakage of machine secrets. To log on to X, you only need to log on as a command line, and then type startx to enter the desktop.
Error 5: Allow at will because you do not understand the permission
If the permission is improperly configured, hackers will be given a chance. The simplest way to handle licensing problems is to use the so-called RWE method, namely, Read, Write, and Execute ). Suppose you want a user to read a file but not write it into it. To do this, you can execute:
Chmod u + w, u-rx file name
Some new users may see an error saying they do not have permission to use the file, so they use the Chmod 777 file name to avoid the problem. But this will actually cause more problems, because it gives the executable permissions of the file. Remember this: 777 grants all users the permission to read, write, and execute a file, and 666 grants all users the permission to read and write a file, in contrast, 555 grants all users the permission to read and execute files, including 444, 333, 222, and 111.
[1] [2] Next page