I saw this problem once, but afterwards was not able to reproduce it. It's a bug in cracklib2 rather than in pam; libpam-cracklib depends on cracklib-runtime, which should take care of setting this all up at install time. Hopefully someone who knows more about the cracklib package can debug this.
I saw this problem once, but afterwards was not able to reproduce it. It's a bug in cracklib2 rather than in pam; libpam-cracklib depends on cracklib-runtime, which should take care of setting this all up at install time. Hopefully someone who knows more about the cracklib package can debug this.