Managing more than 80 Linux servers is not an easy job, but with the help of ssh I can distribute a command to all servers without typing, retyping the password every time for that. Don’t understand me wrong, you will need to type a password for accessing this servers, but just one time. If you manage correctly your keys you will don’t need to have any fear in heavy exploiting the ssh keys.

Share this post

Hide …

When we auditing a Linux system we have a lot of good tools to monitor unexpected changes and unexpected behaviour of a system. Earlier we talked about rkhunter as a system check for rootkits and now, as an alternative, we will talk about chkrootkit (Determine whether the system is infected with a rootkit).

Share this post

Hide Bookmarks

GNU/Linux and other unix operating systems are a very hostile environments for viruses, but they are still in the front of other malware / exploits. The most dangerous malware under GNU/Linux are the rootkits.

Share this post

Hide Bookmarks

Protecting your bootloader is intended for a desktop workstation and not for a production server. Why protecting your bootloader ? Because with a simple boot in single mode a malicious person can change your root password or steal your data. Protecting your bootloader with a password will protect your computer to run in single mode without your permission, but will not protect you to boot from a bootable cd if you don’t also protect your BIOS.

Share this post

…

By default, a Linux, is waiting direct input of a person / sysadmin when is crashing with kernel panic/oops. Obviously is very important to know or to see directly the dumped screen, but sometimes in production environments is better just to reboot itself without any intervention and debug the problem with the system online. Off course for debugging and seeing the dump you will need to install and configure kdump, but that is another story (I will probably write about that soon).

Share this post

…