Skills Delivery: Handling Linux Kernel Security Details

For computer users, the powerful features of Windows serve the majority of users, but Windows security issues still cause headaches for many people, so many people started to use Linux, but the Linux kernel security is not known to be negligent. Today, I will talk about the Linux kernel. Security issues are cleaned up.

Windows security issues are more than fleas in the barn, but Linux may not be immune to its own security holes. Two obvious bugs have been discovered recently, but they were fixed soon. To ensure that you are not bothered, you need to patch your kernel as soon as possible.

The first bug on the fix list is a remote DDos (Distributed Denial of Service) defect that could allow a potential attacker to crash your server by sending an illegal large IPv4 TCP/IP packet. Those network administrators may think: "Wait, have you heard of this stuff?" Yes, you have heard of it.

An old ping to death DDoS attack is back. What happened? According to the Linux kernel discussion list, somewhere between the Linux kernel 2.6.28.10 and 2.6.29 release, someone committed A coding error has caused this ancient attack to come back.

Fortunately - here is still open source - this bug was quickly discovered and fixed before the bad guys with ulterior motives had the chance to attack your system through "ping to death." If you are not using the 2.6.28.1x version of the Linux kernel, then you are safe. Not sure what version you are using? The easiest way is to run the following command at the command prompt:

uname -a

Another bug is much more troublesome in nature because it will cause your system to finish playing. . But then again, you can only do this as a local user, so personally, I don't think it's more important than an attack that can be initiated over the Internet.

This bug is related to the Ext4 file system. In the 2.6.28 kernel, Ext4 has become an official maintenance part. The bug comes from three small Ext4 issues that cause a normal local user to overwrite a file that would otherwise have read access. Therefore, a malicious user can overwrite the original Unix/Linux user password file, '/etc/passwd', regardless of whether they are needed. This is not fun.

This issue has also been fixed. Your usual Linux update operations must be aware of this issue. Is that you make sure your habitual updates are all done?

For Ubuntu; Red Hat; Fedora and openSUSE, there are additional details on fixing these issues. However, unless you want to delve into the details of the code, you don't need to pay too much attention to these confusing things. You just need to make sure that your system is updated normally and everything will be fine.

After completing the processing of the Linux kernel, you can easily use the computer.