Re: Password previously used ideas?
- From: Hugh Oxford <arestes@xxxxxxx>
- Date: Tue, 28 Oct 2008 23:20:50 +0000
Geoff Muldoon wrote:
Hugh Oxford says...
Use a separate table for used passwords, with columns of user, password and date. On an insert check for the number of entries for a user and delete the oldest dated one when the count reaches your threshold. Would also be a much more efficient check for reuse matches.
Geoff M
Of course I _could_ do this but I was looking for a way to avoid it. I don't need to know what the old passwords were, I just need to know that they aren't reusing them.
Does sha1 encode using underscores? I don't think so.
.
- References:
- Password previously used ideas?
- From: Hugh Oxford
- Re: Password previously used ideas?
- From: Geoff Muldoon
- Password previously used ideas?
- Prev by Date: Re: Best development platform? Mac, Windows or Linux?
- Next by Date: Re: image uploads and version control?
- Previous by thread: Re: Password previously used ideas?
- Next by thread: Re: Password previously used ideas?
- Index(es):
Relevant Pages
|