2 ms·
It is a risk trade-off: letting the user reuse passwords used in the last X months is seen as less risky than storing the last 12 passwords (assuming the user i
by dspillett 10y ago
It is a risk trade-off: letting the user reuse passwords used in the last X months is seen as less risky than storing the last 12 passwords (assuming the user is made to cycle their password monthly) if you are storing the credentials securely (if anything is plain or reversible, you need to fix that ASAP).
Having 12 strongly salted+hashed password strings is not going to help an attacker much compared to having 1, even if you use the same salt (though I've not doe the maths myself, you'll need to ask a cryto expert for actual risk figures).
You could of course use a different salt per stored password instead of per user, to mitigate this completely.
Remember that password reuse risk flows both ways: if they reuse the password in your application and your application is well written with regard to securely storing credentials, they may be reusing the same password in another application that is less secure so you are more at the mercy of the password data from elsewhere that is storing things plain.