title: Password hash and salting - is this a good method?
body: <p>I was doing a little research or googling for different methods of handling password hashing and salting and came across this interesting link:</p>
  
  <p><a href="https://web.archive.org/web/20090228183138/http://phix.me/salt" rel="nofollow noreferrer">http://phix.me/salt/</a></p>
  
  <p>Now, essentially what this proposes is the creation of two user functions, one for hashing and one for checking the hash. </p>
  
  <p>The salt is pseudo random but is in actual fact based upon the password (strikes me as bad?).</p>
  
  <p>The hashing function also pseudo randomly "sprinkles" the salt amongst the hash string.</p>
  
  <p>The hash checking function reverses the salt sprinkling and then the actual hash check takes place.</p>
  
  <p>Now, I'm aware that unique salts for each password hash = good, but also that having the logic to hash the passwords and create the salt stored in a db function might = bad.</p>
  
  <p>I like the idea that the salt isn't obvious and that it also needn't be based on some hopefully consistent value such as username, userid, date of birth etc, but as I said I do have my doubts as to the implementation.</p>
  
  <p>So, what are people's opinions and ideas of "best approach solutions"?</p>