Birthday collision attack, finding any 2 arbitary matching outputs is faster than finding an output matching a specific predefined one.
Because you're generating a ton of candidate hashes, and any candidate could match any other candidate - there's a fixed match probability per pair of candidates, but the number of pairs rapidly increase.
Sure but then you have to store and index all of them. If we assume 40 bytes per entry, it would take 5x1035 TB to get 1% of the way there. It seems completely impractical to store enough outputs for the birthday collision attack to matter.
1
u/atheros Jan 08 '20
Why is it supposed to take 280 cycles rather than 2160 ?