Re:How To Safely Store A Password
by pbreit on Friday July 01, 2011 @02:15AM
(#2717231)
Can someone help me understand what a password cracker does with a list of salted/hashed passwords? How do they know they've figured out the right plain text passwords without bouncing them against the authentication logic?
[ Parent
| on HN ]
Re:How To Safely Store A Password
by rorymccune on Friday July 01, 2011 @02:30AM
(#2717255)
Typically attackers do this during an offline brute-force attack (where they have a copy of the hashed password, probably along with other user information from the database).
The attack is done by getting a list of plain text passwords and then running them through the same hashing algorithm as was used originally (adding the salt value if present). Once the attacker has done that they just compare the hashed strings. If they match then it'll be the same password.
Commonly the attacker would start with a dictionary of common passwords and submit them along with common variants (eg, password, Password password1 passw0rd).
If that's not successful they can move onto pure brute force (eg, a , ab, ac, etc)
Re:How To Safely Store A Password
by andrewcooke on Friday July 01, 2011 @07:36AM
(#2717873)
i suspect you don't know that the salt is stored with the password [edit: when using standard libraries like crypt and bcrypt - please don't invent your own scheme]. so when someone steals the password list they get the salt too.
the salt is not "secret" - it is stored in plain text for each password. it does not need to be secret to do its job (defend against rainbow tables).
Sometimes the salt is stored with the password. I sometimes see having a hardcoded salt referred to as 'security by obscurity', but considering that many attacks result in just a database dump, not giving attackers access to (at least part of) the hash is a useful security layer.