Stored passwords with a stronger hash algorithm
Bug #843568 reported by
François Marier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Medium
|
Hugh Davenport |
Bug Description
MD5 is broken, we should switch to something better.
Ideally, we should use PHP 5.3.2's crypt() function (http://
Note that bulk creation of users will be slowed down by using a slow hash. So perhaps in that case, we should use SHA256. Which means that Mahara needs to recognize 3 hash formats at least:
- the existing MD5-hashed passwords
- the new Blowfish ones
- the new SHA256 ones
Changed in mahara: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 1.5.0 |
tags: |
added: passwords removed: password |
Changed in mahara: | |
status: | In Progress → Fix Committed |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Using both Blowfish and SHA256 is not ideal as some users will have stronger passwords than others. We probably may use Blowfish as the main method. With regard of bulk user creation, we indeed can use SHA256 for speed, but upon the login of such user, after SHA256 verification, password hash will be replaced with generated Blowfish one. We might force conversion of existing MD5 passwords to Blowfish as well.