Page MenuHomePhabricator

Implement bcrypt hasher, transparent login upgrade, and explicit upgrade for passwords

Authored by epriestley on Feb 18 2014, 7:06 PM.



Ref T4443.

  • Add a password_hash()-based bcrypt hasher if password_hash() is available.
  • When a user logs in using a password, upgrade their password to the strongest available hash format.
  • On the password settings page:
    • Warn the user if their password uses any algorithm other than the strongest one.
    • Show the algorithm the password uses.
    • Show the best available algorithm.
Test Plan

As an md5 user, viewed password settings page and saw a warning. Logged out. Logged in, got upgraded, no more warning. Changed password, verified database rehash. Logged out, logged in.

Diff Detail

Lint Skipped
Unit Tests Skipped

Event Timeline

epriestley added inline comments.Feb 18 2014, 7:08 PM

The output of md5() has length 32, not 40.


bcrypt has salt embedded in the hash, so we need to be slightly more clever here.


Fixes a bug which is only relevant now that we have two hashers.

epriestley updated this revision to Unknown Object (????).Feb 18 2014, 7:10 PM
  • Fix an issue with comparing md5 signatures.
epriestley updated this revision to Unknown Object (????).Feb 18 2014, 7:13 PM
  • Fix some envelope open/close stuff.
btrahan accepted this revision.Feb 18 2014, 8:11 PM
epriestley closed this revision.Feb 18 2014, 10:09 PM

Closed by commit rP580bcd0d2be4 (authored by @epriestley).