| Summary: | optional cracklib-dicts | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Harald Hoyer <harald> |
| Component: | libpwquality | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | ppisar, tmraz, yselkowi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libpwquality-1.3.0-5.fc25 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-11 15:04:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 1323209 | ||
|
Description
Harald Hoyer
2016-04-01 12:43:28 UTC
How is the dictionary optional? With this default PAM configuration: password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type= an user cannot change his password because it complains on missing dictionary: $ passwd Changing password for user test. Changing password for test. Current password: New password: /usr/share/cracklib/pw_dict.pwd.gz: No such file or directory BAD PASSWORD: The password fails the dictionary check - error loading dictionary New password: Similar issue is with perl-Crypt-Cracklib that also fails with default configuration. I wanted to fix perl-Crypt-Crackli by hard-requiring the cracklib-dicts. But since pam_pwquality.so suffers from the same issue, I must ask whether the dictionary is really option. libpwquality and pam_pwquality allows you to switch off the dictionary check completely. It's just an option in pwquality.conf, use 'dictcheck=0' It is not optional in default configuration however I cannot see how to implement this differently. |