3 ms·
Yes-ish. I don't sweat HMAC-MD5, nor HMAC-SHA-1. What really sucks though is when you can't use them (even though for interop reasons you must) because some s
by cryptonector 9y ago
Yes-ish. I don't sweat HMAC-MD5, nor HMAC-SHA-1. What really sucks though is when you can't use them (even though for interop reasons you must) because some stupid auditor (typically software) goes "oh no! MD5 found!! alert! alert!".
- iRobbery 9y agoHeh heard that one, and the always very convincing answer in a discussion to do or not do certain things... "if it is on the checklist, then.. it is on the checklist"
- cryptonector 9y agoThere is lots of junk on those checklists. Like "must implement n-strikes you're locked", which is idiotic in many contexts.
- azinman2 9y agoFor us who don't know better, could you explain why MD5 or SHA1 are ok in an HMAC context?
- tptacek 9y agoBecause a collision in MD5 doesn't give you a second preimage of an MD5 hash.