If there's some place you can put salts where attackers can't get them, I advise you to put your passwords there too.
It's not a question of can't just forcing them jump though one more hoop. Ideally, no single employee should be able to compromise your system and doing something as simple as xor'ing passwords with 'bob' goes a long way to prevent DBA's from having easy access to everything. So, from a cost benefit standpoint it's obvious to salt your passwords with something.
Edit: I am honestly surprised how much push-back people are giving this without saying why they actually disagree.
Re:Password Security The Right Way
by peterwwillis on Wednesday October 24, 2012 @03:04PM
(#4694488)
Let's completely ignore the fact that most compromises of password databases are of live systems, not extraneous backups. What the hell is the point of the backup? You didn't back up the salts, so restoring the backup leaves you with a broken, useless password database.
So, if say your backups are compromised and someone has all the user names and passwords they still need the salts before they can login to your service.