Construct · 2 fields · 2 citations
One name. One construct. Different systems. One map.
● invariant · one construct, two systems Nearest construct by meaning·not indexedSpokes are the systems the one construct recurs in; dashed arcs are shared lineage. Tap a field for its definition, unit, and measures.
Drag to watch the word get claimed. Each field appears at the publication date of the earliest source cited for it. Tap a year to see which.
The birthday problem is the classic probability result that in a group of only twenty-three people it is more likely than not that two share a birthday, because what matters is the number of pairs, which grows with the square of the group size rather than linearly. More generally, drawing items uniformly from a set of N possibilities, a repeat becomes likely once the number of draws approaches the square root of N. Feller's An Introduction to Probability Theory and Its Applications develops this coincidence counting. The referent is the combinatorics of collisions among random draws from a finite space, the same mathematics that bounds hash collisions in cryptography.[1]
A birthday attack applies exactly the birthday problem against a hash function: because collisions become likely after about the square root of the output space, an attacker expects to find two inputs with the same n-bit digest after roughly 2 to the power n/2 evaluations, far fewer than the 2 to the n a naive search would suggest. This birthday bound is why collision resistance demands digests twice as long as the security level sought. Menezes, van Oorschot, and Vanstone's Handbook of Applied Cryptography presents the attack and its bound. It is the identical collision-counting construct as the birthday problem, realised in the system of hash functions.[2]
Next
See how birthday sits against neighbouring constructs in the Collider, or export every reference on this page in one click.
Open in ColliderExport BibTeXReport this entryCited on this page?
If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.
Claim your construct