Project

General

Profile

Actions

Architecture #24729

open

Allow using a different password hash algorithm for each local user

Added by Alexis Mousset 2 months ago. Updated 4 days ago.

Status:
Pending release
Priority:
N/A
Category:
Security
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No

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.


Subtasks 1 (1 open0 closed)

Architecture #25012: Migrating to bcrypt with unsafe hashes still match bcrypt hash onlyPending releaseFrançois ARMANDActions
Actions #1

Updated by Alexis Mousset 2 months ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions #2

Updated by Alexis Mousset 2 months ago

  • 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
Actions #3

Updated by Clark ANDRIANASOLO 19 days ago

  • Assignee changed from François ARMAND to Alexis Mousset
Actions #4

Updated by Alexis Mousset 11 days ago

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

Updated by Clark ANDRIANASOLO 4 days ago

  • Subtask #25012 added
Actions

Also available in: Atom PDF