Command
pamtester -v auth pknopf authenticate
pamtester: invoking pam_start(auth, pknopf, ...)
pamtester: performing operation - authenticate
Password:
pamtester: Authentication failure
journctl
Feb 06 13:22:17 PAULS-ARCH unix_chkpwd[31998]: check pass; user unknown
Feb 06 13:22:17 PAULS-ARCH unix_chkpwd[31998]: password check failed for user (pknopf)
Feb 06 13:22:17 PAULS-ARCH pamtester[31997]: pam_unix(auth:auth): authentication failure; logname= uid=1000 euid=1000 tty= ruser= rhost= user=pknopf
As it stands right now, every lock screen will prevent me from "unlocking" (KDE lock screen, i3lock
, etc).
If I start i3lock
as sudo
, I can then properly type in the root password to unlock the screen. However, if I run it as normal user, and I can't use normal user or root password to unlock.
Here is my PAM config for i3lock
.
#
# PAM configuration file for the i3lock screen locker. By default, it includes
# the 'system-auth' configuration file (see /etc/pam.d/login)
#
auth include system-auth
Running ls -l /etc/passwd /etc/shadow /etc/group
shows
-rw-r--r-- 1 root root 803 Feb 6 14:16 /etc/group
-rw-r--r-- 1 root root 1005 Feb 6 14:16 /etc/passwd
-rw------- 1 root root 713 Feb 6 14:16 /etc/shadow
This is a fresh install of Arch, so I don't think the configuration is too wonky. What should I be looking for to debug this?
Running ls -l /sbin/unix_chkpwd
shows
-rwxr-xr-x 1 root root 31392 Jun 9 2016 /sbin/unix_chkpwd
pknopf
in your/etc/passwd
, etc., and it can log in? – roaima Feb 6 '18 at 23:45ls -l /sbin/unix_chkpwd
added to your question, please. – roaima Feb 7 '18 at 8:45