Where does obfuscation collide?

In software engineering, obfuscation is deliberately transforming a program so it still runs correctly but is far harder for a human or tool to read, understand, or reverse engineer, used to protect intellectual property and deter tampering. Collberg and Thomborson's 2002 Watermarking, tamper-proofing, and obfuscation — tools for software protection frames it as a practical, best-effort defence measured by the cost it imposes on an attacker rather than by any proof of impossibility. The referent is a heuristic code transformation whose strength is empirical, distinct from the cryptographic notion of obfuscation that aims at a formal security guarantee.[1]

Unit

The effort an attacker needs to understand or undo the transformed code

Recovery means

Not applicable

Measured by

Assessed by potency, resilience, and cost metrics, and empirically by how much it slows reverse engineering

In cryptography, obfuscation is given a precise security target: indistinguishability obfuscation (iO) requires that the obfuscations of any two programs computing the same function be computationally indistinguishable, so no efficient adversary can tell which was obfuscated. Garg, Gentry, Halevi, Raykova, Sahai, and Waters' 2016 Candidate indistinguishability obfuscation and functional encryption for all circuits gave the first candidate construction for all circuits, a result that reshaped theoretical cryptography. The referent is a cryptographic primitive defined by a formal indistinguishability guarantee, unlike the engineering practice of code obfuscation, which offers no such proof despite the shared name.[2]

Unit

Whether obfuscations of two equivalent programs are computationally indistinguishable

Recovery means

Not applicable

Measured by

Established by reduction-based security proofs under stated hardness assumptions, not by empirical attacker effort