Architecture #24729
closed
Allow using a different password hash algorithm for each local user
Added by Alexis Mousset over 1 year ago.
Updated about 1 year ago.
Description
We should be able to derive the hash from the password value, so no need for a global fixed value. Future hash will use a shadow-like format containing the chosen algorithm.
Related issues
2 (2 open — 0 closed)
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5604
- Assignee changed from François ARMAND to Alexis Mousset
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.0~alpha1 which was released today.
- Related to Bug #25293: API documentation for user management in 8.2 added
- Related to deleted (Bug #25293: API documentation for user management in 8.2)
- Related to Bug #27200: Add a global warning and alert banner in user management with unsafe hashes added
- Related to Architecture #27292: Hash in users xml file is not longer relevant with the drop of unsafe hashes added
Also available in: Atom
PDF
Updated by 
Updated by