News for hackers. Stuff that matters.
Re:6.5 Million LinkedIn Password Hashes Leaked by tptacek on Wednesday June 06, 2012 @04:05PM (#4075901)
You're advocating creating a 1MB "salt" string to slow down hashes? That's the same as simply iterating your hash function enough times to invoke the block function repeatedly.

Just use bcrypt, scrypt, or PBKDF2. People have already figured this problem out.

Re:6.5 Million LinkedIn Password Hashes Leaked by romaniv on Wednesday June 06, 2012 @05:21PM (#4076293)
First, I do not advocate anything here. I asked a question.

Second, working with a large string of bits is the same as recursive hashing only if you can pre-compute some small intermediate state of the hash function for that string independently from the password you're trying to guess. If you can't, you would have to work with the entire string for every new password tried.

Re:6.5 Million LinkedIn Password Hashes Leaked by tptacek on Wednesday June 06, 2012 @05:30PM (#4076328)
I answered your question: using a very large "salt" to force a password hash to run more block functions is a bad idea.

Modern password crackers are extremely fast without precomputing anything.