3 ms·
Your theory of salting-per-user is correct. Rainbow tables are useful if the time it takes to compute is big enough that storing a large list is useful. The G
by cmurphycode 13y ago
Your theory of salting-per-user is correct.
Rainbow tables are useful if the time it takes to compute is big enough that storing a large list is useful.
The GPU crackers are so fast nowadays that that isn't the case. If you can try 500M per second, that's about 10 GB of SHA1 generated! Imagine storing a day's worth of work in a rainbow table :)
It's better to use a proper password hash, which will be slow, and will likely have per-user salting built in, anyway.