Password previously used ideas?
- From: Hugh Oxford <arestes@xxxxxxx>
- Date: Tue, 28 Oct 2008 20:23:35 +0000
Hi Folks,
This is more for an intellectual exercise. It's not a difficult problem but it might be interesting to find out different solutions.
So you have users, and they have passwords, stored in SHA1. You have a policy which forces users to change their passwords every month or so. So how to prevent them using two passwords and interchanging them? But they must be able to reuse a password eventually.
I thought a separate db field to which old passwords are appended with a separator, such as _. If the total instances of _ exceed 6, whenever a password is appended, the first one is removed. Then all you do is a substring search to find out if the new password is in this string, and reject it if it is.
But is there a neater way?
.
- Follow-Ups:
- Re: Password previously used ideas?
- From: C. (http://symcbean.blogspot.com/)
- Re: Password previously used ideas?
- From: Geoff Muldoon
- Re: Password previously used ideas?
- Prev by Date: html_entity_decode + regex = profit?
- Next by Date: Re: Password previously used ideas?
- Previous by thread: html_entity_decode + regex = profit?
- Next by thread: Re: Password previously used ideas?
- Index(es):
Relevant Pages
|