What I did was to take the login textboxes off the 'front-page' and move them to another page, when that page is called a session is opened and the 'secret' hidden field is contructed. A randomly created MD5 hash is generated and this becomes the challenge. The challenge and the MD5 hashed password are then hashed again.
The password itself is never sent over and SSL channel, when it is entered at registration time it is hashed ONCE and sent to the server. The hashed password is stored at the server. I do not offer a 'lost password' retrieval, the user can be given the 'hint' that he entered at registration time. But if he still cannot get the password correct we will take him through a process that verifies some of the information in his record and then assigns him a new password.
In reply to Re: Securing Web Apps.
by jdtoronto
in thread Securing Web Apps.
by jdtoronto
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |