Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have modified/etc/login.defs file; PASS_MIN_LEN 8
I have modified /etc.pam.d/system-auth file;
password requisite /lib/security/$ISA/pam-cracklib.so retry=3 minlen=11 1credit=1 ucredit=1 dcredit=1 ocredit=0
Neither modification changes password settings. I still have a default minimum of 6 characters. In the system-auth file it states #User Changes will be destroyed the next time authconfig is run.
Do I need to provoke a program to allow my changes to work. I have rebooted and nothing works. Am I not in the correct files? I have verified that the pam-cracklib.so file is truly located where it is directed to look.
My Linux Operating System has been corrupted (I think it was a password hash I placed in the /boot/grub/grub.conf file that destroyed by OS). Once I rebuild the system today from scratch I will post my system-auth file and allow the forum to review it for accuracy. Sorry about the delay but I will post it as soon as I can rebuild the system.
Using Knoppix 5.1.1 CD I was able to replace two config files (refering to my grub) to defualt and now I can access the linux system, whew!
My earlier problem with passowrd requirement (8 characters - 1 Upper, 1 Lower, 1 Digit and 1 Other) seems to be working for users who want to change their password but when my sys admin, performs a sudo while logged in with this personal (john.frank) and performs the "passwd jane.doe" the sys admin is not forced to use the password minimum requirement; identfied below in the system-auth file. Is this because as sudo, administrators bypass the password requirements found in the system-auth file? Below is my sudoers file and system-auth file.
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth required /lib/security/$ISA/pam_env.so
auth sufficient /lib/security/$ISA/pam_unix.so likeauth nullok
auth required /lib/security/$ISA/pam_deny.so
auth required /lib/security/$ISA/pam_tally.so onerr=fail no_magic_root
session required /lib/security/$ISA/pam_limits.so
session required /lib/security/$ISA/pam_unix.so
# sudoers file.
# This file MUST be edited with the 'visudo' command as root.
# See the sudoers man page for the details on how to write a sudoers file.