Summary: | sys-libs/pam-1.4.0-r1 ebuild change breaks system login | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas Steinmetz <ast> |
Component: | Current packages | Assignee: | Mikle Kolyada (RETIRED) <zlogene> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | da5id2001, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andreas Steinmetz
2020-06-17 09:16:48 UTC
pam pulls correct version of pambase withproper settings. (In reply to Mikle Kolyada from comment #1) > pam pulls correct version of pambase withproper settings. So is this a pambase issue then? I've tried with 20200616 through 20200618, and they all fail ldap auth for me, while local logins are fine. journalctl lists: Jun 18 07:09:46 Rostia login[57932]: PAM adding faulty module: /lib64/security/pam_cracklib.so Jun 18 07:09:46 Rostia login[57932]: PAM unable to dlopen(/lib64/security/pam_cracklib.so): /lib64/security/pam_cracklib.so: cannot open shared object file: No such file or directory (In reply to Brandon Penglase from comment #2) > (In reply to Mikle Kolyada from comment #1) > > pam pulls correct version of pambase withproper settings. > > So is this a pambase issue then? > I've tried with 20200616 through 20200618, and they all fail ldap auth for > me, while local logins are fine. > > journalctl lists: > > Jun 18 07:09:46 Rostia login[57932]: PAM adding faulty module: > /lib64/security/pam_cracklib.so > Jun 18 07:09:46 Rostia login[57932]: PAM unable to > dlopen(/lib64/security/pam_cracklib.so): /lib64/security/pam_cracklib.so: > cannot open shared object file: No such file or directory Sure they will, because pam_cracklib.so does not exist anymore. No, this is not the pambase's problem because cracklib does not exist anymore there as well. All past 3 releases had changes regarding how pam_faillock.so must function, nothing else. |