I have been wondering a lot about different forms of Hashing and such for passwords. Yes I know about salting and would probably add that to the hash, but this is without any salting. I would probably use a dynamic salting technique.
Aside from all of that I was wondering if it was even logical to do what I show below?
<?php
$data = "David";
$hash_crc32 = crc32($data);
$hash_md5 = md5($data);
$hash_sha1 = sha1($data);
echo '<br /><br />' .$hash_crc32. '<br /><br />' .$hash_md5. '<br /><br />' .$hash_sha1;
?>
The Echo Outputs the following:
1180170431
464e07afc9e46359fb480839150595c5
d27937f914ebe99ee315f04449678eccfb658191
$hash_crc32_md5 = $hash_md5 + $hash_crc32 + $hash_sha1 . $hash_md5 . $hash_crc32 . $hash_sha1;
<?php echo '<br /><br />' .$hash_crc32_md5; ?>
That Echo Outputs:
5820170431464e07afc9e46359fb480839150595c51180170431d27937f914ebe99ee315f04449678eccfb658191
So do you think it would be an over kill to hash a password like this? Should I just stick to one form of hashing with salting? I know I cannot be the first to think of something like this as it just seems really obvious.
As well how much harder do you think it would be to run across hashing collision, etc. with this form?
Thanks for any responses! :)