3 ms·
Agreed, in a properly done system as described password hashes shouldn't really be exposed to this, so it's a marginal improvement at best. Where it is importa
by detaro 5y ago
Agreed, in a properly done system as described password hashes shouldn't really be exposed to this, so it's a marginal improvement at best.
Where it is important is cases where the attacker directly supplies the hash: e.g. protocols where the password hashing is done client-side, or HMACs securing tokens and things like that.
I wonder if there is any ecosystem that tries to nudge to this using the type system, e.g. having hash functions return a "HashString" type that will use constant-time comparison functions by default, and needs to be explicitly unwrapped if you want to turn it into a normal string type.