I realize that for security that passwords should not be stored in a DB as plaintext. If I hash them, I can validate them for login purposes.
But if I want to set up a password recovery system, what's the best strategy since there is no undoing of the hashing?
Could someone give me a brief overview of a good and secure strategy for storing and recovering passwords?
You can not recover password that were hashed, neither should you.
What you should do instead is:
You don't 'recover' passwords. What you do is one of 2 things.
My process is as follows.
The user clicks a forgotten password link and then redirected to a reset password form where they are asked to enter their registered email address.
After the user has entered their email address, the system verifies that it exists in the database. If the email address is valid then a token is generated and stored in the database with the users credentials.
An email is sent to the registered email address containing a link to a reset form, the link includes 2 GET parameters including the token and the users unique ID stored in the database.
After the user clicks the link they are taken to the reset form. The system retrieves the 2 GET parameters from the URL and verifies they exist in the database. If the token is verified to exist in the database with the user then the user may be shown the reset password form fields to enter a new password.
I suggest using BCrypt (available since PHP 5.3) to hash the passwords and for additional security, perhaps use some sort of expiration for the token so it can't be used after a period of time.
You can create a new (and randomly generated) password for user, and md5 it , and then send user via email.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With