FS#67372 - [pam] pam_tally not existing anymore breaks sddm autologin

Attached to Project: Arch Linux
Opened by maxi jac (maxi_jac) - Thursday, 23 July 2020, 19:31 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 14 August 2020, 12:45 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Hello,

Description:
After upgrading (from testing),
pam got upgraded to 1.4.0-2 and sddm autologin (maybe simple login also) is now broken because pam_tally.so is not found.
Result is a black screen and impossibility to log into a graphical session at all.

See error log:
sddm-helper[1229]: PAM unable to dlopen(/usr/lib/security/pam_tally.so): /usr/lib/security/pam_tally.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
(Translation: Cannot open shared object: No such file or directory)
sddm-helper[1229]: PAM adding faulty module: /usr/lib/security/pam_tally.so

sddm version 0.18.1-2

I commented the line in /etc/pam.d/sddm-autologin
#auth required pam_tally.so file=/var/log/faillog onerr=succeed

and now it logs in.

Not sure if pam should provide pam_tally.so again or if sddm should drop the dependency to tally.

Steps to reproduce:
sddm 0.18.1-2 + pam 1.4.0-2 and autologin feature enabled => no login, but black screen.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 14 August 2020, 12:45 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.18.1-3
Comment by loqs (loqs) - Thursday, 23 July 2020, 20:05 GMT
gdm uses pam_tally.so in gdm-fingerprint and gdm-smartcard
lightdm uses pam_tally.so in lightdm-autolongin
Comment by Paweł Baranowski (pavbaranov) - Monday, 27 July 2020, 08:38 GMT
This bug is probably the same as:  FS#67347 
Comment by loqs (loqs) - Friday, 07 August 2020, 00:16 GMT
pam_faillock.diff uses pam_faillock preauth to reject authentication to users that have exceeded the tally limit.
It does not record failures or reset the tally count on success.
   pam-faillock.diff (0.5 KiB)

Loading...