in reply to
Re^8: On showing the weakness in the MD5 digest function and getting bitten by scalar context
in thread On showing the weakness in the MD5 digest function and getting bitten by scalar context
Yes, it's probably possible to come up with a workaround that would allow us to continue using MD5 securely, much like triple DES allows us to keep using DES. Now that there's a good alternative to DES, though (namely AES), there's no reason to keep using triple DES (which is slow). There's already a good alternative to MD5, so there's no reason to kludge up a workaround.
Note that nobody ever uses double DES. That's because it is vulnerable to a meet-in-the-middle attack. Secure workarounds are hard to design.