SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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 an application that authenticates users, but it only works when run as root, and when it's told to use PAM (doesn't work when it's told to use shadow file).
Users other than root are not able to run the application to authenticate users by either using shadow (kind of understandable as it needs root to see shadow) or PAM. So, a non-root user is unable to run the application to authenticate users.
The application uses the 'login' service.
This is what uname -a looks like:
Linux kamet 22.214.171.124-0.8-xen #1 SMP Mon Jul 3 18:25:39 UTC 2006 i686 i686 i386 GNU/Linux
login file (/etc/pam.d/login) is as follows:
#auth required pam_securetty.so
auth include common-auth
auth required pam_nologin.so
account include common-account
password include common-password
session include common-session
session required pam_lastlog.so nowtmp
session required pam_resmgr.so
session optional pam_mail.so standard
common-auth (/etc/pam.d/common-auth) is as follows:
Quite obviously, the password is perfectly correct, and /etc/shadow has it as follows (patqa2 being the user name):
THE BIG QUESTION:
What's going on?
Any help would be greatly appreciated as I'm not really sure what's going on with this!
The tool is owned by the user patqa2.
hmm well if file doesnt have a permissions to access your PAM auth file then it will fail, it is like shadow file in this case, you have passwd(644)file that has read access for everybody so any script can view it, and then passwd itself is owned by root, has a permission to access shadow. so i assume you should have same schema here, or what you can try to do is to change permissions for your PAM to 644 so it can be read by all users...