Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

TLDR: Use PBKDF2 or scrypt instead.

PBKDF2 has had longer public exposure, and also features an adjustable CPU work factor (though with a lower theoretical safety-to-compute-time than bcrypt).

scrypt is newer, but features both a CPU and memory work factor (memory-hard algorithm), and is algorithmically superior to both.



> PBKDF2 has had longer public exposure

I don't know whether or not it's had more public exposure, but I don't think it's had longer public exposure. Afaik, bcrypt's canonical reference document is the June 1999 Usenix paper (http://static.usenix.org/event/usenix99/provos/provos_html/i...), while PBKDF2's is the September 2000 RFC (http://www.ietf.org/rfc/rfc2898.txt).


Thanks for the reference, didn't realize that, though I think that's what the article was implying.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

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

Search: