3 ms·
The issue is not bcrypt vs. some other hash. The issue is hashing vs. reversible encryption. Unix has been using salted hashed passwords since the 70s. "one-wa
by kevinpet 13y ago
The issue is not bcrypt vs. some other hash. The issue is hashing vs. reversible encryption.
Unix has been using salted hashed passwords since the 70s. "one-way hash function" is a common phrase in the first edition of Applied Cryptography published in 1994. http://books.google.com/books?q=isbn:0471597562 http://books.google.com/books?q=isbn:0471597562
- tedunangst 13y agoWorth noting that Gawker got shat on precisely for using unix salted passwords, so what you're saying isn't the issue is at least some of the issue.
- deleted 13y ago[deleted]
- bigiain 13y agoActually, here on HN, "Use bcrypt" has been the war-cry whenever password storage is discussed for quite some time - mostly linking to Coda Hale's blog post from 2010: http://codahale.com/how-to-safely-store-a-password/ http://codahale.com/how-to-safely-store-a-password/ (the discussions usually then fragment into the "No, use scrypt instead! GPUs! HashCat! ASICs! Memory-hard vs iterations-hard!" thread, and the "but what if I use an application salt with my MD5 hashes? Or invent my own complification techniques (and keep using MD5)?")