Project

General

Profile

Actions

Architecture #25012

closed

Architecture #24729: Allow using a different password hash algorithm for each local user

Migrating to bcrypt with unsafe hashes still match bcrypt hash only

Added by Clark ANDRIANASOLO 4 months ago. Updated 3 months ago.

Status:
Released
Priority:
N/A
Category:
Security
Target version:
Effort required:
Small
Name check:
To do
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

Actions #1

Updated by Clark ANDRIANASOLO 4 months ago

  • Status changed from New to In progress
Actions #2

Updated by Clark ANDRIANASOLO 4 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
Actions #3

Updated by Clark ANDRIANASOLO 4 months ago

  • Status changed from Pending technical review to Pending release
Actions #4

Updated by Alexis Mousset 3 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

Also available in: Atom PDF