3 ms·
OMG, that's all I can say.I'm no expert on security, but the few web sites that I wrote, I intuitively tried to do something as complicated as possible... e.g.
by tomp 15y ago
OMG, that's all I can say.I'm no expert on security, but the few web sites that I wrote, I intuitively tried to do something as complicated as possible... e.g.
md5('something silly' + password + 'qtjwtrb89ujq309')
Now, if I were to make an authentication system again, I would use custom salt for every user, something like
sha1('random1' + username + 'random2' + password + 'random3')
This way, there is no way to use rainbow tables or something like that.
- deleted 15y ago[deleted]
- LukeShu 15y agoThat's better, but still horribly broken. Sha1 and md5 simply aren't adequate for secure passwords, they are still broken too quickly. You should use bcrypt. http://codahale.com/how-to-safely-store-a-password/ http://codahale.com/how-to-safely-store-a-password/ explains why, and links to implementations of bcrypt in many environments/languages (in the opening when he says "Use bcrypt" a hundred times).
- tomp 15y agothanks. I had something like that in mind, but didn't know what it was called.
- kogir 15y agoTo beat the dead horse one more time, please use per-user salts and bcrypt, scrypt, or PBKDF2 (RFC 2898). Single time hashes (even per-user salted), are no longer sufficient protection.
- mapgrep 15y agoI think you mean "PBKDF2 with thousands or tens of thousands of iterations," not single iteration like RIM was using :) http://blog.crackpassword.com/2010/09/smartphone-forensics-cracking-blackberry-backup-passwords/ http://blog.crackpassword.com/2010/09/smartphone-forensics-c...