Skip to main content
Topic: PAM (Read 2137 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

PAM

(Trying to su to root on laptop) "su: Authentication service cannot retrieve authentication info" so I added to su in /etc/pam.d:
    "auth sufficient pam_succeed_if.so user ingroup admin"
which group I had created as root and user is member, but same message.  Do I have to put user in sudoers.d?  Trying to understand PAM.  Any advice deeply appreciated.

Re: PAM

Reply #1

What about:

Code: [Select]
sudo -i
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

sudo

Reply #2
Thanks, lq, probably good solution.  In fact I'm worried whether my PAM is ok.  I looked at sudo and not being a vim aficionado, set an environment variable SUDO_EDITOR to nano.  Maybe no need.  A few configuration things sounded like yesterday's solution and I got syntax errors using visudo so I might stick to PAM.  Heaven knows PAM syntax is far from intuitive either.

PAM

Reply #3
Has anyone had the message "Authentication service cannot retrieve authentication info"?  What do I have to do to fix PAM?

PAM

Reply #4
I moved question to Forum  JHendry

PAM

Reply #5
If anyone could shed some light on "Authentication service cannot retrieve authentication info", I'd be most obliged.  Also how to delete a thread I started.

PAM

Reply #6
Would PAM be affected if I changed the owner:group  of PAM files from root:root to root:admin and perm to 775 so other admins can administer it?  Only 1 laptop, not a commercial enterprise at all.

PAM, sudo

Reply #7
Just for interest and because I have a problem with PAM at the moment and because someone suggested I use sudo, PAM and sudo are compatible, right?  It's not the case that sudo is an older solution and PAM a better one.  Old is not necessarily rusty, is it, and I daresay the interface using visudo has stood the test of time.    I suppose I wonder which packages are maintained and which aren't and how to find out.

Re: PAM, sudo

Reply #8
Sudo already depends on PAM for a long time, if you want to bypass that run
Code: [Select]
su -c 'command'

@JHendry I merged all of your past four threads, to delete one go to More - Remove.

Your current issue is about "Authentication service cannot retrieve authentication info", did this happen after modifying what exactly, /etc/sudoers or something else?

PAM

Reply #9
  Thx for combining thread, hitman, problem persists.  I get the error attempting su from another user.  Other user is in admin group with root.  Most of my files were installed with owner:group root:root.  I used chgrp to make them root:admin and permission 775.  This is so I can administer the system as the other user and perform one task in particular (install LFS).  Btw "more.." doesn't  offer me "remove".


sudo

Reply #11
Pardon my ignorance of sudo, lq, and thx for the link.    I see it has advantages over su but can't I do without both by appropriate groups and PAM files?

Re: PAM

Reply #12
Just for interest and because I have a problem with PAM at the moment and because someone suggested I use sudo, PAM and sudo are compatible, right?  It's not the case that sudo is an older solution and PAM a better one.  Old is not necessarily rusty, is it, and I daresay the interface using visudo has stood the test of time.    I suppose I wonder which packages are maintained and which aren't and how to find out.


how can you use sudo without pam?  https://www.redhat.com/sysadmin/pluggable-authentication-modules-pam

pam has been the authenication agent for Linux for maybe decades.

Re: PAM

Reply #13
  I don't want to use sudo without PAM, mtbrklyn, I want PAM in working order.  The error message "authentication service cannot retrieve authentication info" suggests it may not be.  So I wondered if I had mucked up the permissions.

Re: PAM

Reply #14
  I don't want to use sudo without PAM, mtbrklyn, I want PAM in working order.  The error message "authentication service cannot retrieve authentication info" suggests it may not be.  So I wondered if I had mucked up the permissions.


It suggests to me you don't have a root user in /etc/passwd or something like that.  It says it can't find it, not that it is not working.


It can't be you have no root user.