One more variable to throw into the mix. The new versus olde passwords have different lengths. If you look at the length of the password first, you can then determine which password function to use to authenticate. -----Original message----- From: "Bob Meetin - 303-926-0167 - www.dottedi.biz" bobm at dottedi.biz Date: Wed, 15 Aug 2007 11:39:39 -0700 To: "thelist at lists.evolt.org" thelist at lists.evolt.org Subject: Re: [thelist] md5 hashed password problem > Thank you so much- we have blast off. I need to write up some steps to > turn this into a conversion-type routine, but the result was that it > woks to authenticate and grant access. I think what i need to do is > > 1) set old password off for original members and authenticate, > 2) capture the password that they entered to successfully authenticate, > 3) convert to the new scheme, and > 4) change them from flagged, historic to regular. > > Or something thereabouts. Unless I am missing something it seems that I > should be able to add a password flag field to the members table and use > an if/else to update this field. Sorry Hassan but this is not ugly and > annoying to me, more like a life-saver as well as a learning > experience! I will let y'all know when I have this working.