Whatever you can do online with a GPU, you can do much in an offline session stored in a file.
Sharing rainbow tables over the internet is probably dead, but your disks can keep more hashes than you can calculate quickly.
Sharing rainbow tables over the internet is probably dead, but your disks can keep more hashes than you can calculate quickly.
I used MD5 because that's the typical hash you find unsalted on leaks, but if you do the math with others it is almost impossible to find an example where storing beats using a GPU to crack (even an older one) for a couple of hours.
Is the idea that password hashes should be slow relatively new?
It's just that security wasn't as important (limited web attack surface) or generally understood back in the day (so people were even less likely to ask "is this hash suitable for passwords rather than checksums/indexing/etc?" than they are today), or the slow ones from then were fine -then-, but advances in hardware, the availability of the cloud/GPUs (so massive parallelization without a cost of infrastructure only a nation state could afford), etc, means they're easily compromised today.
The idea that password hashes should be slow is indeed relatively new. Also it's contemporary to the idea that algorithms should have salts builtin, so those features usually go together.