Actions
Architecture #25012
closedArchitecture #24729: Allow using a different password hash algorithm for each local user
Migrating to bcrypt with unsafe hashes still match bcrypt hash only
Fix check:
To do
Regression:
No
Description
Even with unsafe-hashes="true"
in the rudder users XML file, after upgrading to 8.2, it seems that the previous unsalted hashes are not tested against the login password : users could no longer log in unless their hash is actually a bcrypt one
Updated by Clark ANDRIANASOLO 5 months ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 5 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5726
Updated by Clark ANDRIANASOLO 5 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|e30298aa831dedc147a3dd249c231a7f8fd40e46.
Updated by Alexis Mousset 4 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.0~alpha1 which was released today.
Actions