Managing RHEV VMs Via the Virsh CLI

Out of the box you are not going to be able to run virsh commands on the cli as root. Libvirt, Virsh, and KVM are just not that tightly integrated in RHEV. You can however, follow the procedure below, and create a user and password to use for authentication. # saslpasswd2 -a libvirt fatminPassword:Again (for … Continue reading Managing RHEV VMs Via the Virsh CLI

Password Protecting Grub in RHEL 6

Grub, is the standard boot loader used by each and every Linux type operating system that I can think of. RHEL 6 uses what I guess we are now calling grub 1.o, since grub 2.0 has been released and in use by Fedora for the last few releases. You will also find that grub 2.0 has replaced grub 1.0 in RHEL 7. At some point I plan to explore grub 2 at lenght, but today is not that day (unless something strange happens before I go to bed tonight -- you never know).

Fun With PAM: Working with pam_cracklib and pam_tally2

Plugable Authentication Modules, or PAM, is the standard mechanism that most Unix and Linux Operatng Systems use for user credential authentication. By design, PAM is broken out into a number of files, each with a specific purpose. Before you can get started with PAM you need to understand a bit about how PAM configuration files are formatted. So lets get into that first before we try to bite off anything more.

Enycrypting Passwords Via SSL for Redhat Kickstart Configuration Files

Hello again earthlings. The fatmin returns once again to dispense a bit of wisdom. This handy one-liner is a command that for the life of me I cannot remember. Our story begings when building your kickstart config and post-install config files you are going to need to set the password for at least one user … Continue reading Enycrypting Passwords Via SSL for Redhat Kickstart Configuration Files

You are not allowed to access to (crontab) because of pam configuration.

PD Donut Guy with ShadowHey look a real live Linux post. Sure enough and right as rain I am back with something that is not about networking (yea!) and not about Solaris (yuck). In this case we had a user who is in our database team who was attempting to make modifications to the oracle user's crontab. However they kept running into the error below