Authors: Zademn, ireland Reviewed by:
Prerequisites
Probability theory (for the main idea)
Hashes (an application)
Motivation
Breaking a hash function (insert story)
*insert story / introduction about why it's called a paradox + use*
Question 1
What is the probability that 1 person has the same birthday as you?
Solution
Let be the event that someone has the same birthday as you and be the complementary event
The events are mutually exclusive =>
Let be the events that person does not have your birthday
Then
Question 2
Suppose the birthdays are distributed independently and uniformly
Solution
Question 1
Question 2
Code examples
Algorithm
Example:
Consider the following hash function:
We make the following function to find the hashes:
We use it as follows:
This is done by choosing the next input based on the hash of the previous input, according to the following sequence:
Therefore, we can detect that a collision has occurred by using standard cycle-detection algorithms, such as Floyd's tortoise and hare!
And finally, we can locate the first place in the sequence where the collision occurred, which will let us determine what the colliding inputs to the hash function are. This is done by determining how many iterations apart the colliding inputs are, and then stepping together one iteration at a time until the collision occurs.
This is implemented in the following code snippet.
https://en.wikipedia.org/wiki/Birthday_problem - wiki entry
https://en.wikipedia.org/wiki/Birthday_attack - wiki entry
https://www.youtube.com/watch?v=ofTb57aZHZs - vsauce2 video
Reminder: if are independent events
What is the probability that 2 out of people in a room share the same birthday?
Let be the event that 2 people have the same birthday, let be the complementary event (no 2 people have the same birthday)
Event 1 = Person 1 is born =>
Event 2 = Person 2 is born on a different day than Person 1 =>
Event n = Person n is born on a different day than Person
Instead of days we have
Instead of days we have
From the Taylor approximation we know for Apply for each event:
If we want to solve for knowing we take the =>
Let be a hash function with
Let's denote
1. Choose random distinct messages in
2. Compute for
3. Look for If not found go to step 1
While the above algorithm works to find a hash collision in time , it also requires storing hash values. As such, it represents a classic time-space tradeoff over the naive approach, which involves randomly selecting pairs of inputs until they hash to the same value. While the naive approach does not require any additional storage, it does have runtime .
However, there is a better approach combining the best of both worlds: constant storage requirements and runtime. This approach is based on Pollard's Rho algorithm, which is better-known for its application to solving discrete logarithms. The core insight behind the algorithm is that by the Birthday Paradox, we expect to encounter a hash collision after trying random inputs. However, it is possible to detect whether a collision has occurred without needing to store all of the inputs and hashes if the inputs are chosen in a clever way.
Where is our hash function and is a "sufficiently random" function which takes a hash value and produces a new. We define the composition of the functions to be.
By the Birthday Paradox, we expect that the sequence will have a collision (where for two distinct values ) after values. But once this occurs, then the sequence will begin to cycle, because .
For Floyd's tortoise and hare, this is done by noting that when we found our collision after iterations, we were comparing . And because the sequence is cyclic, if the first colliding input is , then it collides with. So we define the new sequence , and step through the and sequences together until we find our collision!
Finally, there is a third algorithm for finding hash collisions in time, namely the van Oorschot-Wiener algorithm based on Distinguished Points. While it does have additional storage requirements over Pollard's Rho, the main advantage of this algorithm is that it parallelizes extremely well, achieving runtime when run on processors.