Posts

Showing posts from April, 2014

OpenSSL CVE-2014-0160 Heartbleed bug and Red Hat Enterprise Linux

OpenSSL CVE-2014-0160 Heartbleed bug and Red Hat Enterprise Linux Issue Does CVE-2014-0160 affect Red Hat Enterprise Linux? Need fix for openssl heartbleed bug What versions of Red Hat Enterprise Linux are affected by openssl heartbleed vulnerability? Do we have a list of packages/services we ship with RHEL that need a restart after OpenSSL has been updated? Environment Red Hat Enterprise Linux 7 Release Candidate (RC) not affected Red Hat Enterprise Linux 7 Beta affected Red Hat Enterprise Linux 6 affected Red Hat Enterprise Linu

Linux Boot Process

Image
Press the power button on your system, and after few moments you see the Linux login prompt. Have you ever wondered what happens behind the scenes from the time you press the power button until the Linux login prompt appears? The following are the 6 high level stages of a typical Linux boot process. 1. BIOS BIOS stands for Basic Input/Output System Performs some system integrity checks Searches, loads, and executes the boot loader program. It looks for boot loader in floppy, cd-rom, or hard drive. You can press a key (typically F12 of F2, but it depends on your system) during the BIOS startup to change the boot sequence. Once the boot loader program is detected and loaded into the memory, BIOS gives the control to it. So, in simple terms BIOS loads and executes the MBR boot loader. 2. MBR MBR stands for Master Boot Record. It is located in the 1st sector of the bootable disk. Typically /dev/hda, or /dev/sda MBR is less than 512 bytes in size. This has three

Unlock Linux accounts which are locked by PAM_tally2

pam_tally2 module is used to lock user accounts after certain number of failed ssh login attempts made to the system. This module keeps the count of attempted accesses and too many failed attempts. pam_tally2 module comes in two parts, one is pam_tally2.so and another is pam_tally2 . It is based on PAM module and can be used to examine and manipulate the counter file. It can display user login attempts counts, set counts on individual basis, unlock all user counts. By default, pam_tally2 module is already installed on the most of the Linux distributions and it is controlled by PAM package itself. This article demonstrates on how to lock and unlock SSH accounts after reaching a certain failed number of login attempts. How to Lock and Unlock User Accounts Use ‘ /etc/pam.d/password-auth ‘ configuration file to configure login attempts accesses. Open this file and add the following AUTH configuration line to it at beginning of the ‘ auth ‘ section.   auth