3 ms·
Most of your traffic should be coming from people with logged in cookies. If you make people enter their password on every page, you won't have to worry about
by tedunangst 15y ago
Most of your traffic should be coming from people with logged in cookies. If you make people enter their password on every page, you won't have to worry about high volume. :)
Note that bcrypt is basically insensitive to length of password. 4 chars, 8 chars, 32 chars, all take the same amount of time. And it's tunable. You could go down to only 0.01s per hash and still be a million times slower than plain MD5.
- darrenkopp 15y agoI don't think he's talking about users... I think he's talking about high volume web services.
- nl 15y agoWebservices usually use signed requested[1][2] for security, not username/password pairs. [1] http://oauth.net/core/1.0/#signing_process http://oauth.net/core/1.0/#signing_process [2] http://en.wikipedia.org/wiki/WS-Security#Features http://en.wikipedia.org/wiki/WS-Security#Features