Your application requires users to log on with a user name and password. You are implementing a method that uses the SHA1Managed class to hash the password to store. You need to create a hash of the password while minimizing the risk of a dictionary attack.

What should you do to minimize the risk of a dictionary attack?

One of the problems with the Hash algorithms presented thus far is that if two users happen to use the same password, the hash will become exactly the same value. If a malicious user looks at your table that stores passwords, the malicious user will find patterns and know that most likely people are using common words. The malicious user can then start a dictionary attack to try to determine the passwords. One way to ensure that no two users' passwords hash to the same value is to add a unique value to each person's password before hashing it. This unique value is called a "salt" value. When you do this, you will need to ensure that you store the salt value used as a part of the user's record.