Quote:
|
Originally Posted by hobolooter
Also wasting resources? C'mon man. Don't post if you are just going to be making stuff up. An MD5 hash calculation on a 16 byte string is ridiculous to even consider a resource hog.
|
Hashing is quite CPU intensive compared to other tasks. Obviously if you have a website that isn't busy, and is on a dedicated server, then you should be fine. But if you are designing the login for Google accounts, then you need something as efficient as you can get.
MD5 hashing isn't secure anymore, you should use SHA-512 instead, and salt the hash rather than hashing multiple times.