asp.net - Correctly Salting a Hash in .NET -


i implementing new password stored procedure companies current product. asp.net application ms sql server.

before used 3des encryption off same common seed encrypt, , check users authentication decrypted password using same seed.

i implementing sha256 hash, salt can not decrypted.

firstly, understand every salt should different per user, don't understand salt stored? if stored in database, doesn't void purpose?

my idea creating salt taking first 4 letters of username, first 3 letters of first name, , first 3 letters of last name, , converting md5 hash , using salt without storing in database.

this sequence server side no hacker know sequence without source code.

is there issues doing here?

also sha256 acceptable or should looking @ sha512.

thanks

"is there issues doing here?"

yes, there is. obscurity not security. because salt hard find out doesn't mean it's secure. figuring out how created salt piece of cake compared forcing hash.

there no need keep salt secret, create random number each user , store along password. purpose of salt elliminate advantages of using rainbow tables crack passwords in table. salt have different users (preferably unique, that's not crucial).


Comments

Popular posts from this blog

apache - Remove .php and add trailing slash in url using htaccess not loading css -

javascript - jQuery show full size image on click -