yeah, i looked at the NIST specs for the hashing algorithm and i didn't see anything that would be affected by some external (to the algorithm) change. so i think you're right. it either has to be the input or the db. this happened to me as well as the users and i am POSITIVE that i typed the password in properly. can't really blame it on user error :)
thanks for helping me think about this and narrow down the possibilities. -----Original Message----- From: Sisyphus [mailto:[EMAIL PROTECTED] Sent: Wed 11/16/2005 9:39 PM To: Wiswell, Virginia; [email protected] Cc: Subject: Re: Digest::SHA1 weirdness ----- Original Message ----- From: "Wiswell, Virginia" > After a few days, Digest::SHA1 starts creating a > different digest for the identical password. Very unlikely. More likely that the "identical password" is no longer identical - and you should be concentrating on finding out how that happens. Or perhaps the value stored on the database has been corrupted. The only way $vi_digest will change is if $vi_data changes. If you think it's worth it, you could use Digest::SHA (or even Digest::MD5) instead - and see if that fixes the problem. I would be very surprised if it did. Cheers, Rob _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
