onlist this time... tedd wrote: > > <snip> > > > > I think the MD5() hash is a pretty good way and if the weakness is the > > user's lack of uniqueness in determining their passwords, then we can > > focus on that problem instead of looking to another hash. And besides, > > the solution presented was to create a salt and use that -- that's > > just another step in the algorithm process not much different than > > what I propose. > > > > Cheers, > > > > tedd > > > The MD5 hash IS the problem. The problem isn't the uniqueness of the passwords, but rather the uniqueness of the hash. The solution is to use another hash that does not have the same collision issues. Thank you, Micah Gersten onShore Networks Internal Developer http://www.onshore.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
