FS#30313 - [sudo]Wrong PAM config file makes sudo not to work

Attached to Project: Arch Linux
Opened by Adam (adam900710) - Saturday, 16 June 2012, 08:43 GMT
Last edited by Allan McRae (Allan) - Saturday, 16 June 2012, 09:53 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

sudo 1.8.5.p2-1 doesn't work correctly, even the password is correct, it still
says "password incorrect" and can't gain root privilege.

Additional info:
sudo 1.8.5.p2-1
If replace the config file in /etc/pam.d/sudo with /etc/pam.d/su,
sudo works again.

The audit log shows the following messages:
------
Jun 16 16:34:56 adam-vm sudo: PAM no modules loaded for `sudo' service
Jun 16 16:34:58 adam-vm sudo: PAM no modules loaded for `sudo' service
Jun 16 16:34:59 adam-vm sudo: PAM no modules loaded for `sudo' service
------

Steps to reproduce:
1) Update sudo to the given version.
2) Execute sudo -v command and enter the right password.
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 16 June 2012, 09:53 GMT
Reason for closing:  Not a bug
Comment by Allan McRae (Allan) - Saturday, 16 June 2012, 09:44 GMT
Sounds like you made changes to the sudo pam file that caused the breakage. The default pam file works fine.
Comment by Adam (adam900710) - Saturday, 16 June 2012, 09:47 GMT
No changes to sudo pam file, but /etc/pam.d/other seems not the full version,
the content is the same with the sudo pam file.
(two line about account).

Reinstalling pambase seems to repair the breakage.

Loading...