prevent them from compromising all the accounts quickly
No, it prevents them from quickly finding accounts with weak passwords
certainly does not prevent them from targeting selected accounts. If the have both the hash and the salt, it becomes a matter of cpu cycles, and with AWS and other selling those so cheaply, it is just a matter of how much they are prepared to spend.
Oh, really? Could you estimate how much it will cost to crack 16 characters random alphanumeric password (let's assume we're using SHA512)? And how many CPUs do I need if I want it this life? Maybe CPU cycles not exactly the right thing in this case.
In reply to Re^4: SaltedDigest Salt?
by zwon
in thread SaltedDigest Salt?
by packetstormer
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |