Hacker News new | past | comments | ask | show | jobs | submit login

Hashing takes a lot of CPU time. And btw you don't even need to change the database schema. You could encode the version in the password field itself. Django does this and it works great



The database would contain existing passwords without normalization. You also you have to hold the unnormalized password. Super silly to do that to save a few processor cycles on login.


It's amazing how much misinformation is in this thread. You should do further reading on password hashing and rethink whether you really have to store two different passwords...


Hashing one or two 10 char strings takes basically no time on even old mobile hardware.


Good password hash algorithms specifically are designed to take a while. They add latency to the subsequent page load when you click “submit”.


Not if you are using algorithms specifically designed to take a lot of CPU time, which is a best practice

https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpubli...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: