>>Hi,
>>
>>I am designing a new module where each user would have to be assigned a user name/id and password. This information will be stored in a SQL Server table. I have two questions:
>>1. Is it acceptable practice to store the user name/id un-encrypted (readable by anyone)?
>>2. What method of encrypting the password would you recommend (does not have to be Super Secure) that later can be used by another (e.g. .NET) application?
>>
>>TIA
>
>
>Store hash of the password. this way nobody can decrypt it including you
First, thank you. If there is a simple example of how to hash a password, please let me know. For example, user wants his password to be '123'. How do you store it as hash to a table.field PassFile.UserPwrd?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
