https://bugzilla.suse.com/show_bug.cgi?id=1171318 https://bugzilla.suse.com/show_bug.cgi?id=1171318#c10 --- Comment #10 from Arvin Schnell <aschnell@suse.com> --- (In reply to Thorsten Kukuk from comment #8)

Else yast2 security will stop working or create broken PAM configuration files if pam_cracklib get's removed with one of the next PAM releases.

That is already the case. Since PAM adds pwquality when adding cracklib, YaST is already not able to show the correct status. And setting the minlen using cracklib seems to have no effect whatsoever. # pam-config --add --cracklib pam_cracklib used, replacing with pam_pwquality. d9:~ # pam-config --add --cracklib-minlen=8 d9:~ # pam-config --query --cracklib d9:~ # pam-config --query --pwquality -- You are receiving this mail because: You are on the CC list for the bug.