You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently noticed that sites protected with basic auth were very slow to respond. After some research we pinpointed this to using a strong crypt_scheme (sha256_crypt) to hash passwords.
We had hoped to easily resolve this by changing crypt_scheme to apr_md5_crypt (the default). However, after changing this and doing an ansible run all htpasswd files remained unchanged.
Summary
We recently noticed that sites protected with basic auth were very slow to respond. After some research we pinpointed this to using a strong crypt_scheme (sha256_crypt) to hash passwords.
We had hoped to easily resolve this by changing crypt_scheme to apr_md5_crypt (the default). However, after changing this and doing an ansible run all htpasswd files remained unchanged.
Copied from ansible/ansible#66802, but the problem still persists.
Issue Type
Bug Report
Component Name
htpasswd
Ansible Version
Community.general Version
Configuration
OS / Environment
On the server passlib==1.7.1
Steps to Reproduce
Start of with a task similar to this:
Run ansible.
Then change
crypt_scheme
toapr_md5_crypt
Run ansible again.
Expected Results
I expected the htpasswd files to be updated with the password hashed using the configured crypt_scheme.
Actual Results
The htpasswd files remain unchanged.
Ansible logs: [user] already present
Code of Conduct
The text was updated successfully, but these errors were encountered: