3 ms·
I have to disagree with this point Despite plenty of guidance to the contrary, the first point is really not where we want to be. The problem with doing th
by stephenr 14y ago
I have to disagree with this point
Despite plenty of guidance to the contrary, the first point is really not where we want to be. The problem with doing this is that it means a persistent password – one you can go back with and use any time
If a developer can't work out how to implement a one-use password that forces a password change after login, they shouldn't be writing code.
- Deregibus 14y agoThat puts the onus on the user to immediately log in after receiving the temporary password. Until they do (which could be months later), they have their password to the site stored in email. The DoS issue that was mentioned in the next paragraph is also a pretty good reason to use a reset link instead.
- stephenr 14y agoSo you're suggesting that a user who goes to a site to login, and can't (forgotten password) will then completely lose any and all reason to login to the site, AFTER doing what's required for a new random password to be generated and sent to them? Sounds pretty far fetched to me.