# Is there a standard one way function that does not produce collision

Is there any standard or accepted one way function that does not produce collisions? I'm not looking for hash functions.

Does that make sense at all? for example given string with length n, the function will always output same obfuscated string that is not possible to reverse engineer. something that is mathematically one way function but also doesn't produce collision.

So I don't want to store the actual input, but just a successor of input that cant be decrypted at all, this will be used only to see if duplicate input is received or not.

• Does it have to be keyless or can you just use AES in ECB mode? – Elias Jun 26 '17 at 20:37
• It sounds like you're looking for ​ one-way injections . ​ ​ ​ ​ – user991 Jun 26 '17 at 20:40
• crypto.stackexchange.com/questions/48601/… may have some related insights regarding function collisions... – Paul Uszak Jun 26 '17 at 20:59
• Is it necessary that the input be arbitrary in size? – Daffy Jun 27 '17 at 2:04

• @M.kazemAkhgary I don't think it's possible to have a $\{0,1\}^* \rightarrow \{0,1\}^*$ transformation such that the output gives no information about the input, and is resistant to preimage attacks. – Daffy Jun 27 '17 at 2:02
The easiest way to be sure that there are no collisions in a function is for it to have an inverse, but in your case we don't want to be able to actually compute the inverse. It seems like we can use some kind of public key solution, where we have destroyed the private key. For instance, choose sufficiently large $p$ and $q$ and define a one-way function as $h = m^e \mod p*q$. If you had kept $d$ (or $p$ or $q$) you could get back $m$, but without it it's not practical. For large enough message values you'll need to break the input into blocks, and you'll want to chain the blocks together if partial matches leak information in your case.