Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
	I just tried to change the root password. The final idea is to deploy a script to change root password in bulk, to many machines at once.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
	I tried this command:
	echo "bruno:amjr0000" | sudo chpasswd
   * What was the outcome of this action?
	/var/cache/cracklib/cracklib_dict.pwd: No such file or directory
	BAD PASSWORD: The password fails the dictionary check - error loading dictionary
   * What outcome did you expect instead?
	I expected the password would change.
*** End of the template - remove these template lines ***

Control: reassign -1 libpam-cracklib

Seems to be a problem in libpam-cracklib or your local
configuration.

Please provide the output of these commands:

  dpkg -l libpam-cracklib cracklib2-runtime

  cat /etc/pam.d/passwd

  cat /etc/pam.d/common-password


Chris

Hello Chris.

Thank you for your prompt response. The outputs you've asked are following
bellow.

Regards,
Bruno

*dpkg -l libpam-cracklib cracklib2-runtime:*
dpkg-query: no packages found matching libpam-cracklib
dpkg-query: no packages found matching cracklib2-runtime

*cat /etc/pam.d/passwd:*
#
# The PAM configuration file for the Shadow `passwd' service
#

@include common-password

*cat /etc/pam.d/common-password:*
#
# The PAM configuration file for the Shadow `passwd' service
#

@include common-password

bruno@B-desktop:/etc/pam.d$ cat /etc/pam.d/common-password
#
# /etc/pam.d/common-password - password-related modules common to all
services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of modules that define the services to be
# used to change user passwords.  The default is pam_unix.

# Explanation of pam_unix options:
# The "yescrypt" option enables
#hashed passwords using the yescrypt algorithm, introduced in Debian
#11.  Without this option, the default is Unix crypt.  Prior releases
#used the option "sha512"; if a shadow password hash will be shared
#between Debian 11 and older releases replace "yescrypt" with "sha512"
#for compatibility .  The "obscure" option replaces the old
#`OBSCURE_CHECKS_ENAB' option in login.defs.  See the pam_unix manpage
#for other options.

# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
password        requisite                       pam_pwquality.so retry=3
password        [success=1 default=ignore]      pam_unix.so obscure
use_authtok try_first_pass yescrypt
# here's the fallback if no module succeeds
password        requisite                       pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
password        required                        pam_permit.so
# and here are more per-package modules (the "Additional" block)
# end of pam-auth-update config

Hi libpam-pwquality maintainers,

looks like you're the correct people to handle the bug below.
[..]
[..]

Chris