• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Cryptographic vs. One-Way hash?

Lazy8s

Golden Member
I have an assignment where I need to define a cryptographic hash message (whuch I did) but the very next question was to define a one-way hash.....

This really caught me off guard for a minute. I can answer each question easily, but when I saw them right next to eachother it made me start to think...what IS the difference? A cryptographic hash is one way, easy to compute and has no collisions....A one-way hash function is a hash in which the hashed message cannot be derived from the hash value. But they are also supposed to be computationally simple and a good one will be collision free as well!!

Obviously, a OWHF does not HAVE to be collision free but it sure wouldn't have much value if it wasn't.

What is your take?
 
Umm, no hash function is collision free. By definition, a hashing function will take a variable length input and produce a fixed length output. Because there is an infinte amount of inputs and a finite number of possible outputs, there will always be collisions. However, the likelihood of collisions gets more and more unlikely as the length of the hash output increases.

As for "cryptographic hash message," I've never heard of that term, and apparently neither has Google. Are you sure you're not referring to Message Authentication Code or Keyed-hash Message Authentication Code??
 
Back
Top