Password Validation based on the frequency of occurence

> Can you be more specific on the idea given technically

What am I missing? Store the last 20 passwords and the date of creation in a database. Before you allow a new password, check to see if it is already in the database. Once you have accepted a new password then update the database.

sabre150a at 2007-7-11 23:31:48 >

> Thanks a lot

> Actually i want to do it without creating seperate

> table in the database to store the password history.

>

> i already did by creating a table but trying to do

> find out whether there is any other way witout

> creating table in the db.

>

> Thanks

Serialize the passwords (or their hash):

http://java.sun.com/developer/technicalArticles/Programming/serialization/

prometheuzza at 2007-7-11 23:31:48 >

> Thanks a lot

> Actually i want to do it without creating seperate

> table in the database to store the password history.

>

> i already did by creating a table but trying to do

> find out whether there is any other way witout

> creating table in the db.

I really must be missing something. You have to store the passwords (or at least a hash of each of them) somewhere and if you already have a database then why not there? If you don't, how are you going to know which ones have been used.

I don't see that serialization will help.

Message was edited by:

sabre150

sabre150a at 2007-7-11 23:31:48 >

> ...

> I think Serialization was proposed in case it was

> storing them specifically in the DB that was the hang

> up (as opposed to storing them in general)

I thought the OP said he didn't want to store them in a DB. Now that I read back, I see that the OP wrote s/he didn't want to create a table [in the DB] for it.

Guess I was a bit fed up with the OP pleas for "more details", that I didn't really read his posts... Sorry about that (to the OP as well of course!).

; )

prometheuzza at 2007-7-11 23:31:48 >