asp.net - Hashing vs. Encrypting Passwords -


i'm using asp.net membership site serve sophisticated users. understand difference between hashed , encrypted passwords, , i'm trying decide between two.

after last client complained bitterly hashed passwords being total pita, i've started favor encrypted passwords. suggested isn't secure enough.

so question is: what, risks of encrypting passwords? person ability steal passwords decrypting them database surely have ability reset them if hashed, no? i'm having trouble seeing cause trouble encrypted passwords couldn't hashed ones. making convenient users important.

the risk decryptable passwords people use 1 password various logins , accounts, not application dealing with.

  • with encrypted password, stolen/decrypted password tried out on users' other accounts (e.g. stolen banking password lead access email).
  • with hashed password, there no recovery. theft of password hashes should never yield usable passwords

treat passwords property of account owner. it's not yours view, decrypt, or other things with. if user forgets password, offer reset, , not retrieval.


Comments

Popular posts from this blog

python - Scipy curvefit RuntimeError:Optimal parameters not found: Number of calls to function has reached maxfev = 1000 -

c# - How to add a new treeview at the selected node? -

java - netbeans "Please wait - classpath scanning in progress..." -