pam_sm_chauthtok missing, and automatic pam-auth-update causing problems

Asked by Gordon Good

When I install libpam-tacplus_1.3.7-1_amd64.deb, one of the package scripts seems to run "pam-auth-update tacplus", as the files /etc/pam.d/common-* are updated to include libpam-tacplus.

The problem is that common-password is modified, but it appears that the pam_sm_chauthtok symbol isn't present in the library. This causes the PAM password service to fail, and the following message appears in /var/log/auth.log

Aug 16 23:17:54 192-168-3-4 passwd[6070]: PAM unable to resolve symbol: pam_sm_chauthtok

Perhaps the module in the Ubuntu distro is being compiled without PAM_SM_PASSWORD defined?

As a side note, if the package install scripts automatically runs pam-auth-update tacplus, it makes it impossible to include libpam-tacplus in a distro. This is because configuration for libtacplus is added to the common-* files, but no TACACS+ server is configured. This causes all logins to fail with the following (in auth.log):

Aug 16 23:15:30 192-168-3-4 PAM-tacplus[6022]: TACACS+ service type not configured

We've tried to create an appliance that contains libpam-tacplus, but after installation, it's impossible to log in for the reason stated above. The only way to recover is to boot into single-user mode and unconfigure libpam-tacplus (or point it at a TACACS+ server).

I suppose we could work around this by running pam-auth-update -r tacplus, later in our appliance install process, but I would prefer if pam-auth-update were not run automatically on package install.

Thanks

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu libpam-tacplus Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

i suggest you report a bug

Revision history for this message
Danny Spell (ddspell) said :
#2

I know this post is old (9 years ago!) and who knows if you're still around, but did you ever solve this issue?

I'm having the same problem.

Revision history for this message
Danny Spell (ddspell) said :
#3

Actually, I have the answer now.

Having an independent PAM settings file in /etc/pam.d won't work.

You have to add your module parameters to the lines inserted into:
common-account
common-auth
common-password
common-session
common-session-noninteractive

Can you help with this problem?

Provide an answer of your own, or ask Gordon Good for more information if necessary.

To post a message you must log in.