Actions
Bug #13643
closedIn Rudder 5.0, user password encoding is broken for some passwords.
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Priority:
79
Name check:
Fix check:
Regression:
Description
The algorithm used for user password encoding that compare them to the one stored in file may lead to a surnumerary leading '0'.
It's only on some passwords, so using an other password is sufficient to workaround the problem.
Updated by François ARMAND about 6 years ago
The problem is in the hexa string encoding. Using bouncy castle encoder resolve the problem.
Updated by François ARMAND about 6 years ago
- Status changed from New to In progress
Updated by François ARMAND about 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2045
Updated by François ARMAND about 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|aaaa33a2eb9afd31fe59ad217c7ffb2efc6ad0d1.
Updated by Vincent MEMBRÉ about 6 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.1 which was released today.
Changelog
Actions