security - Best way to store password in database -

I am working on a project that has authentication (user name / pass)

this Also connects to a database, so I thought I would store the username and password there, but it seems that the table sitting on DB should not have a password as a text field, there is no such good idea. >

Using C # and by 2008 Express Server Ekt Does anyone get the idea (possibly the best way of many examples) to store this type of data?

(I am open to the idea that this information is not stored in DB if a good reason can be provided)

You are right that accumulating a password in a plain-text field is an awesome idea, however, as long as it stays , in most cases you (and I honestly can not think of any counter-example) in a passport in the representation database The proper job is to represent I mean that you want to have a password (which should be different for each user) and use a secure 1-way algorithm to heath the password and that After you want to throw away the original password, when you want to check a password, you compare the value of the value (by using the same hashing algorithm and salt) and the database in the database.

So, when it's a good thing to think about and it's a good question, it's actually at least one duplicate of these questions:

To make a bit more clear, the danger of having a password stored and storing it is that if an encroachment is holding your database, then they can still use the password that has the "decrypt" password ( Less Less than those visible in the rainbow table) are known as. To get around this, developers add a password, which is done properly, attacks the rainbow that are unable to do only. Note that a common misconception is to add a uniform unique and long string only for all passwords; While it is not awesome , it is best to add unique salts for each password.