Yeah that's the one
So even if your password was 'password' the system would assign the salt to your password, say '541t' making your password '541tpassword'. If someone has the password hash and is trying passwords until they find one that gives the same hash as yours then this stops them using a list of known passwords or a dictionary.
To make the system stronger you can have random salt values assigned to each user which are stored at a different location. Assuming an attacker got hold of the database containing the password hashes, unless they have the list of unique salts they'd have a hard job identifying the password as the salt has increased the password length.
Using this type also protects against rainbow tables which are huge lists of hashes and the passwords that made them. These tables take a long time to compute int he first place but then mean discovering the password takes seconds. With a large enough salt the time needed to create and store the rainbow table becomes unmanageable.
That's about as much as I know on the subject so if any of it's inaccurate please feel free to correct.
Nick
So even if your password was 'password' the system would assign the salt to your password, say '541t' making your password '541tpassword'. If someone has the password hash and is trying passwords until they find one that gives the same hash as yours then this stops them using a list of known passwords or a dictionary.
To make the system stronger you can have random salt values assigned to each user which are stored at a different location. Assuming an attacker got hold of the database containing the password hashes, unless they have the list of unique salts they'd have a hard job identifying the password as the salt has increased the password length.
Using this type also protects against rainbow tables which are huge lists of hashes and the passwords that made them. These tables take a long time to compute int he first place but then mean discovering the password takes seconds. With a large enough salt the time needed to create and store the rainbow table becomes unmanageable.
That's about as much as I know on the subject so if any of it's inaccurate please feel free to correct.
Nick