Do I have to keep my salt in the same column as my hash?
So, I'm cool with using a [per-user salt][1] to hash my users' passwords. However, there's one piece of advice in the [accepted answer][2]: 

> Do not use a separate column for the salt.

This doesn't make sense to me. If I'm just catenating the hash and salt and putting them in the same column, surely that's semantically equivalent to two separate columns? In which case, that's just security-by-obscurity, no?

It's easier to use a separate column to store the salt (as long as it's per-user). Why shouldn't I?


  [1]: http://stackoverflow.com/questions/2188507/help-with-salt-and-passwords
  [2]: http://stackoverflow.com/questions/2188507/help-with-salt-and-passwords/2188556#2188556salt.
Do I have to keep my salt in the same column as my hash?
===

So, I'm cool with using a [per-user salt][1] to hash my users' passwords. However, there's one piece of advice in the [accepted answer][2]: 

> Do not use a separate column for the salt.

This doesn't make sense to me. If I'm just catenating the hash and salt and putting them in the same column, surely that's semantically equivalent to two separate columns? In which case, that's just security-by-obscurity, no?

It's easier to use a separate column to store the salt (as long as it's per-user). Why shouldn't I?


  [1]: http://stackoverflow.com/questions/2188507/help-with-salt-and-passwords
  [2]: http://stackoverflow.com/questions/2188507/help-with-salt-and-passwords/2188556#2188556salt.