-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Password change fails when using cracklib dictionary check on a subtree/user password policy #6270
Comments
Hi, |
AddressSanitizer detects heap use after free:
For some reason I can't get better symbols, addr2line fails too, even though all debuginfo data is installed. |
Indeed there is a problem about how new_passwdPolicy handles pwdpolicy->pw_dict_path |
Hi there, thank you for spending the time looking into this. Can confirm creating the subtree pwdpolicy without |
Issue Description
When I have a subtree or user password policy applied with pwdchecksyntax and pwddictcheck both on and pwddictpath pointing to cracklib dictionary, changing the password of users with the policy applied will fail with a 'No such file or directory' error (see screenshot). The dictionary file definitely exists at the right location.
Same error also if the subtree policy inherits from global policy that has all three options set.
This however, is not an issue if only used with a global policy and not applied at subtree/user level.
Package Version and Platform:
Steps to Reproduce
Steps to reproduce the behavior:
dsconf -D "cn=Directory Manager" -W ldap://localhost:389 localpwp addsubtree "ou=users,dc=test,dc=com,dc=au"
dsconf -D "cn=Directory Manager" -W ldap://localhost:389 localpwp set --pwdchecksyntax=on --pwddictcheck=on --pwddictpath=/usr/share/cracklib/pw_dict "ou=users,dc=test,dc=com,dc=au"
Expected results
Password change successful after running it through cracklib dictionary check
Screenshots
CLI:
389ds log:
Additional context
I have not being able to test this on a different platform.
The text was updated successfully, but these errors were encountered: