That's great - thanks. Points on their way.
s46.
Main Topics
Browse All TopicsHi,
I am working on a web app with an ASP.NET front end (forms authentication), a VB.NET COM layer and a SQL Server database. I am storing the password as an MD5 hash value, then re-computing the value each time the user logs in. So far this is working fine, but I have been reading that it is better to add a random salt value to the end of the password, and store this in the user table for use when re-computing the password hash (see http://msdn.microsoft.com/
Full marks for the first person who gives an unequivocal reason why I should use a salt value as described in the above link.
s46.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: NeedPointsPosted on 2005-06-27 at 07:03:56ID: 14308679
The article doesn't explain the concept much, so it is normal that you didn't understand the point.
om/article print.aspx ? quickid=0 411121&pri ntmode=tru e
"In addition, storing just the password, even hashed, isn't good enough. If an interloper can get access to your database, and if many users share the same password (no matter how hard you try, users still use stupid words like "password" as their password), a determined hacker might be able to ascertain a pattern and attempt a dictionary attack, trying common combinations of letters and numbers, based on patterns seen in the hashed passwords. To work around this potential security hole, most systems employ a second-level of misdirection in the form of a random "salt" value hashed along with the actual password. "
From : http://www.code-magazine.c
So, this salt thing is for someone who somehow accesses the hashed passwords.
Hacker grouped the hashed passwords in the table, and saw that five users have the same password, so their passwords are probably 'password' or '' something common and stupid like that.
But when you salt them, probably every hashed password in the database will be different. So a hacker can't estimate something out of it.