First time users get an automatically generated cryptic password.
You could reuse this.
Problem is you can't overwrite the old password yet, because you can't know who requested the reset.
You'll need a page password_reset asking for the reset_password which is stored separately.
Additionally you need a timestamp and a counter to limit the numbers of requests.
Otherwise an attacker could spam a user with useless requests. (Tho he needs to know the name of the account and the email to do so)
In hindsight, the code creating a new user should already have a mechanism to block spamming an email by restricting the number of attempts.
I tried to look into Create A New User, but it wasn't evident for me if that's already handled.
Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery
In reply to Re^16: Ideas for "fixing" PerlMonks 1.0
by LanX
in thread Ideas for "fixing" PerlMonks 1.0
by etj
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |