I think your post is being downvoted because it seems to conflate cryptographic primitives with tools that you can use without modification to safely store a password.
I think your post is being downvoted because it seems to conflate cryptographic primitives with tools that you can use without modification to safely store a password.
Fun fact, by the way: there aren't any practical attacks on HMAC-MD5.
This has nothing to do with passwords. You can read about brokenness of RC4, MD5, or SHA1 in their respective Wikipedia articles.
BTW, suggested reading: http://cr.yp.to/talks.html#2013.03.12 ("Failures of secret-key cryptography").
And thanks for that link. Slide 313 is terrifying.
I'm not talking about signing my microsoft update cert with md5() here.
By all means, I do encourage you to get a valid token for the next 20 minutes, find a collision attack and get a secure token that will work for another timestamp "sometime in the future" (without passing the captcha!) on the system I'm building..
Asking other people (especially, not professional cryptographers) to try to break your system which knowingly uses insecure primitives is an awful way to evaluate system security.