Description of problem: I found in the journal of cauldron VM: su[3457]: PAM unable to dlopen(/usr/lib64/security/pam_cracklib.so): /usr/lib64/security/pam_cracklib.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichi> su[3457]: PAM adding faulty module: /usr/lib64/security/pam_cracklib.so in /etc grep -R pam_cracklib.so pam.d/system-auth:password required pam_cracklib.so try_first_pass retry=3 minlen=4 dcredit=0 ucredit=0 But nothing provides pam_cracklib.so https://github.com/linux-pam/linux-pam/blob/master/NEWS : Removed deprecated pam_cracklib module, use pam_passwdqc (from passwdqc project) or pam_pwquality (from libpwquality project) instead. Cauldron provides only pam_pwquality, thus the update should modify /etc/pam.d/system-auth to substitute pam_pwquality to pam_cracklib
Version: 8 => Cauldron
It's fixed since pam-1.5.1-2.mga9.
Papoteur's report is for the most recent version in Cauldron, 1.5.2. If what you say is correct, has there been a reversion?
CC: (none) => lewyssmith
nope, but we dont modify config files in /etc on update, so if the system was installed before the fix, it will still be there...
How will this be handled on upgrades from Mageia 8?
CC: (none) => davidwhodgins
(In reply to Thomas Backlund from comment #3) > nope, > but we dont modify config files in /etc on update, so if the system was > installed before the fix, it will still be there... Noted. And you cannot uninstall (to re-install) PAM... It breaks the system. Is there anything Papoteur can do to stop the reported error? Will it not affect anyone with a Cauldron system installed before v1.5.1 (Aug 2021)?
CC: (none) => zen25000
I installed Cauldron using the urpmi method from a MGA8x86 VM (Fully updated sept 21), Installed MGA8 from scratch jul 18 2022 The install date for the Cauldron is sep 22 2022 I hit that issue and Dave Hodgins asked to search an opened bug or remember "Regarding the messages about pam_cracklib.so, the module has been deprecated. While the messages don't appear to cause any problem, the various rules in /etc/pam.d/ will need to be fixed to no longer require it. Please open a bug report if there isn't one already. Regards, Dave Hodgins" If is required further testing, I can export my MGA8x86 That is fully updated and redo the migration in other VM to avoid service disruption
CC: (none) => neoser10
*** Bug 30949 has been marked as a duplicate of this bug. ***
CC: (none) => bequimao.de
Shouldn't the config file(s) requiring pam_cracklib.so be renamed to *.rpmsave and a new one created?
nope. .rpmsave is only created if one removes a package that contains a %config file that has been modified. I guess to cope with upgrades we might need to do some specific sed surgery on upgrade
(In reply to Thomas Backlund from comment #9) > nope. > > .rpmsave is only created if one removes a package that contains a %config > file that has been modified. > > > I guess to cope with upgrades we might need to do some specific sed surgery > on upgrade Would be nice if that could be done, too, for users already running cauldron since before pam-1.5.1-2.mga9 Assignning to the base system maintainers
CC: (none) => marja11Assignee: bugsquad => basesystem
Thanks Marja.
CC: lewyssmith => (none)
Is this still valid in current pam-1.5.2-5 or pam-1.5.2-5.1 from https://bugs.mageia.org/show_bug.cgi?id=32746#c2 ?