Reads like Chatty was a bit annoyed at you. And it remains the expert, not you!
You kind of have to push LLMs to self-evaluate for good answers, although I am not sure what I would take from this on a technical level. I would use MD5 for non-security applications, I even think you could use it in a security context if you really know how collisions can be created and if that would interfere with your application of it. Better advice is to not do that of course.
Although thinking about it. What are non-security applications of hashes? Database indexing comes to mind, where a collision avoidance is the opposite you want. So what remains? For file integrity I would use SHA-2 something, but I don't see how MD5 would perform worse. Are there more obvious applications?
Perhaps the initial answer isn't really technically correct, but I wouldn't say it is bad advice.
1 comment
[ 3.2 ms ] story [ 12.0 ms ] threadYou kind of have to push LLMs to self-evaluate for good answers, although I am not sure what I would take from this on a technical level. I would use MD5 for non-security applications, I even think you could use it in a security context if you really know how collisions can be created and if that would interfere with your application of it. Better advice is to not do that of course.
Although thinking about it. What are non-security applications of hashes? Database indexing comes to mind, where a collision avoidance is the opposite you want. So what remains? For file integrity I would use SHA-2 something, but I don't see how MD5 would perform worse. Are there more obvious applications?
Perhaps the initial answer isn't really technically correct, but I wouldn't say it is bad advice.