Red HatThis forum is for the discussion of Red Hat Linux.
Notices
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.
We are doing a security audit of the lab I work at and one of the problems I was given to solve was if the /etc/pam.d/common-account file needs to be in our pam.d setup. Also if so, what it should contain.
After researching a little it seems to me that this module will perform common checks on all accounts that log into the system, i.e. if the account is still valid, password has expired, and any other global checks / restrictions.
This leads me to believe that the file should be included and a good content would be:
'account required /lib/security/pam_unix.so'
I was wondering if anyone could agree with me or offer any suggestions.
Hmmm, I do see that 'account required /lib/security/pam_unix.so' is already in system-auth. So why do I see examples of people using /etc/pam.d/common-account? Isn't that a little redundant?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.