Meet-in-the-middle attack

From TCS Wiki
Revision as of 09:45, 20 October 2014 by imported>Carriearchdale (WPCleaner v1.33 - Fixed using Wikipedia:WikiProject Check Wikipedia (Template with Unicode control characters))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Template:Complex The Meet-in-the-middle attack is a cryptographic attack which, like the birthday attack, makes use of a space-time tradeoff. While the birthday attack attempts to find two values in the domain of a function that map to the same value in its range, the meet-in-the-middle attack attempts to find a value in each of the ranges and domains of the composition of two functions such that the forward mapping of one through the first function is the same as the inverse image of the other through the second function—quite literally meeting in the middle of the composed function.

It was first developed as an attack on an attempted expansion of a block cipher by Diffie and Hellman in 1977. When trying to improve the security of a block cipher, one might get the idea to simply use two independent keys to encrypt the data twice and think that this would square the security of the double-encryption scheme. Certainly, an exhaustive search of all possible combination of keys would take [math]\displaystyle{ 2^{2n} }[/math] attempts if each key is n bits long, compared to the [math]\displaystyle{ 2^n }[/math] attempts required for a single key. However, Diffie and Hellman, discovered a time-memory tradeoff that could break the scheme in only double the time to break the single-encryption scheme.[1] The attack works by encrypting from one end and decrypting from the other end, thus meeting in the middle.

Assume the attacker knows a set of plaintext and ciphertext: P and C. That is,

[math]\displaystyle{ C=E_{K_2}(E_{K_1}(P)) }[/math],

where E is the encryption function (cipher), and K1 and K2 are the two keys.

The attacker can then compute EK(P) for all possible keys K and store the results in memory. Afterwards he can decrypt the ciphertext by computing DK(C) for each K. Any matches between these two resulting sets are likely to reveal the correct keys. (To speed up the comparison, the EK(P) set is stored in an in-memory lookup table, then each DK(C) can be matched against the values in the lookup table to find the candidate keys.)

Once the matches are discovered, they can be verified with a second test-set of plaintext and ciphertext. If the keysize is n, this attack uses only [math]\displaystyle{ 2^{n+1} }[/math] encryptions (and [math]\displaystyle{ O(2^n) }[/math] space) in contrast to the naive attack, which needs [math]\displaystyle{ 2^{2n} }[/math] encryptions (but only [math]\displaystyle{ O(1) }[/math] space).

Other pages

References

Template:Math-stub