CRDec 16, 2014

How many queries are needed to distinguish a truncated random permutation from a random function?

arXiv:1412.5204v127 citations
Originality Incremental advance
AI Analysis

This addresses a fundamental cryptographic security problem for designing pseudorandom functions and permutations, but it is incremental as it builds on prior work to extend and tighten bounds.

The paper tackles the problem of distinguishing a truncated random permutation from a random function using queries, showing that Ω(2^{(m+n)/2}) queries are needed for non-negligible advantage and that a 1978 result provides a better bound, which is tight in some cases.

An oracle chooses a function $f$ from the set of $n$ bits strings to itself, which is either a randomly chosen permutation or a randomly chosen function. When queried by an $n$-bit string $w$, the oracle computes $f(w)$, truncates the $m$ last bits, and returns only the first $n-m$ bits of $f(w)$. How many queries does a querying adversary need to submit in order to distinguish the truncated permutation from the (truncated) function? In 1998, Hall et al. showed an algorithm for determining (with high probability) whether or not $f$ is a permutation, using $O(2^{\frac{m+n}{2}})$ queries. They also showed that if $m < n/7$, a smaller number of queries will not suffice. For $m > n/7$, their method gives a weaker bound. In this note, we first show how a modification of the approximation method used by Hall et al. can solve the problem completely. It extends the result to practically any $m$, showing that $Ω(2^{\frac{m+n}{2}})$ queries are needed to get a non-negligible distinguishing advantage. However, more surprisingly, a better bound for the distinguishing advantage can be obtained from a result of Stam published, in a different context, already in 1978. We also show that, at least in some cases, Stam's bound is tight.

Foundations

The foundational work for this paper's niche, ranked by how specifically the neighbourhood builds on it — not by global fame.

Your Notes