# Indistinguishability obfuscation

In cryptography, indistinguishability obfuscation (abbreviated IO or iO) is a type of software obfuscation with the defining property that obfuscating any two programs that compute the same mathematical function results in programs that cannot be distinguished from each other. Informally, such obfuscation hides the implementation of a program while still allowing users to run it.[1] Formally, IO satisfies the property that obfuscations of two circuits of the same size which implement the same function are computationally indistinguishable.[2]

Indistinguishability obfuscation has several interesting theoretical properties. Firstly, iO is the "best-possible" obfuscation (in the sense that any secret about a program that can be hidden by any obfuscator at all can also be hidden by iO). Secondly, iO can be used to construct nearly the entire gamut of cryptographic primitives, including both mundane ones such as public-key cryptography and more exotic ones such as deniable encryption and functional encryption (which are types of cryptography that no-one previously knew how to construct[3]), but with the notable exception of collision-resistant hash function families. For this reason, it has been referred to as "crypto-complete". Lastly, unlike many other kinds of cryptography, indistinguishability obfuscation continues to exist even if P=NP (though it would have to be constructed differently in this case), though this does not necessarily imply that iO exists unconditionally.

Though the idea of cryptographic software obfuscation has been around since 1996, indistinguishability obfuscation was first proposed by Barak et al. (2001), who proved that iO exists if P=NP is the case. For the P!=NP case (which is harder, but also more plausible[2]), progress was slower: Garg et al. (2013)[4] proposed a construction of iO based on a computational hardness assumption relating to multilinear maps, but this assumption was later disproven. A construction based on "well-founded assumptions" (hardness assumptions that have been well-studied by cryptographers, and thus widely assumed secure) had to wait until Jain, Lin, and Sahai (2020). (Even so, one of these assumptions used in the 2020 proposal is not secure against quantum computers.)

Currently known indistinguishability obfuscation candidates are very far from being practical. As measured by a 2017 paper[needs update], even obfuscating the toy function which outputs the logical conjunction of its thirty-two Boolean data type inputs produces a program nearly a dozen gigabytes large.

## Formal definition

Let ${\displaystyle {\mathcal {iO}}}$ be some uniform probabilistic polynomial-time algorithm. Then ${\displaystyle {\mathcal {iO}}}$ is called an indistinguishability obfuscator if and only if it satisfies both of the following two statements:[5][6][7]

• Completeness or Functionality: For any Boolean circuit C of input length n and input ${\displaystyle x\in \{0,1\}^{n}}$, we have
${\displaystyle \Pr[C'(x)=C(x):C'\leftarrow {\mathcal {iO}}(C)]=1.}$
• Indistinguishability: For every pair of circuits ${\displaystyle C_{0},C_{1}}$ of the same size k that implement the same functionality, the distributions ${\displaystyle \{{\mathcal {iO}}(C_{0})\}}$ and ${\displaystyle \{{\mathcal {iO}}(C_{1})\}}$ are computationally indistinguishable. In other words, for any probabilistic polynomial-time adversary A, there is a negligible function ${\displaystyle \varepsilon (k)}$ (i.e., a function that eventually grows slower than ${\displaystyle 1/p(k)}$ for any polynomial p) such that, for every pair of circuits ${\displaystyle C_{0},C_{1}}$ of the same size k that implement the same functionality, we have
${\displaystyle |\Pr[A({\mathcal {iO}}(C_{0}))=1]-\Pr[A({\mathcal {iO}}(C_{1}))=1]|\leq \varepsilon (k).}$

## History

The origin of this idea came from Amit Sahai in 1996 from the notion of a zero-knowledge proof.[8]

In 2001, Barak et al., showing that black-box obfuscation is impossible, also proposed the idea of an indistinguishability obfuscator, and constructed an inefficient one.[8][7][2]Although this notion seemed relatively weak, Goldwasser and Rothblum (2007) showed that an efficient indistinguishability obfuscator would be a best-possible obfuscator, and any best-possible obfuscator would be an indistinguishability obfuscator.[8][9] (However, for inefficient obfuscators, no best-possible obfuscator exists unless the polynomial hierarchy collapses to the second level.[9])

### Candidate constructions

Barak et al. (2001) proved that an inefficient indistinguishability obfuscator exists for circuits; that is, the lexicographically first circuit that computes the same function.[7] If P = NP holds, then an indistinguishability obfuscator exists, even though no other kind of cryptography would also exist.[2]

A candidate construction of IO with provable security under concrete hardness assumptions relating to multilinear maps was published by Garg et al. (2013),[2][10][3] but this assumption was later invalidated.[10][3] (Previously, Garg, Gentry, and Halevi (2012) had constructed a candidate version of a multilinear map based on heuristic assumptions.[4])

Starting from 2016, Lin began to explore constructions of IO based on less strict versions of multilinear maps, constructing a candidate based on maps of degree up to 30, and eventually a candidate based on maps of degree up to 3.[3] Finally, in 2020, Jain, Lin, and Sahai proposed a construction of IO based on the symmetric external Diffie-Helman, learning with errors, and learning plus noise assumptions,[3][5] as well as the existence of a super-linear stretch pseudorandom generator in the function class NC0.[5] (The existence of pseudorandom generators in NC0 (even with sub-linear stretch) was a long-standing open problem until 2006.[11]) It is possible that this construction could be broken with quantum computing, but there is an alternative construction that may be secure even against that (although the latter relies on less established security assumptions).[3][speculation?]

### Practicality?

There have been attempts to implement and benchmark IO candidates.[2] For example, as of 2017, an obfuscation of the function ${\displaystyle x_{1}\wedge x_{2}\wedge \dots \wedge x_{32}}$ at a security level of 80 bits took 23.5 minutes to produce and measured 11.6 GB, with an evaluation time of 77 ms.[2] Additionally, an obfuscation of the Advanced Encryption Standard encryption circuit at a security level of 128 bits would measure 18 PB and have an evaluation time of about 272 years.[2]

An open-source software implementation of an IO candidate was created in 2015.[12]

## Existence

It is useful to divide the question of the existence of iO by using Russell Impagliazzo's "five worlds",[13] which are five different hypothetical situations about average-case complexity:[6]

• Algorithmica: In this case P = NP, but iO exists.
• Heuristica: In this case NP problems are easy on average; iO does not exist.[dubious ]
• Pessiland: In this case, ${\displaystyle BPP\neq NP}$, but one-way functions do not exist; as a result, iO does not exist.
• Minicrypt: In this case, one-way functions exist, but secure public-key cryptography does not; iO does not exist (because explicit constructions of public-key cryptography from iO and one-way functions are known).
• Cryptomania: In this case, secure public-key cryptography exists; iO is believed to exist in this case.[improper synthesis?] (The subcase of cryptomania in which iO does exist is known as obfustopia.[14][15])

## Potential applications

Indistinguishability obfuscators, if they exist, could be used for an enormous range of cryptographic applications, so much so that it has been referred to as a "central hub" for cryptography,[1][3] the "crown jewel of cryptography",[3] or "crypto-complete".[2] Concretely, an indistinguishability obfuscator (with the additional assumption of the existence of one-way functions[2]) could be used to construct the following kinds of cryptography:

Additionally, if iO and one-way functions exist, then problems in the PPAD complexity class are provably hard.[5][19]

However, indistinguishability obfuscation cannot be used to construct every possible cryptographic protocol: for example, no black-box construction can convert an indistinguishability obfuscator to a collision-resistant hash function family, even with a trapdoor permutation, unless with an exponential loss of security.[20]

## References

1. ^ a b Klarreich, Erica (2014-02-03). "Cryptography Breakthrough Could Make Software Unhackable". Quanta Magazine.
2. Pellet--Mary, Alice (26 May 2020). "Co6GC: Program Obfuscation | COSIC". www.esat.kuleuven.be. Archived from the original on 11 November 2020. Retrieved 22 August 2021.
3. Klarreich, Erica (2020-10-10). "Computer Scientists Achieve 'Crown Jewel' of Cryptography". Quanta Magazine.
4. ^ a b Barak, Boaz (29 December 2020). "New Developments in Indistinguishability Obfuscation (iO) | Simons Institute for the Theory of Computing". simons.berkeley.edu. Retrieved 22 August 2021.{{cite web}}: CS1 maint: url-status (link)
5. Jain, Aayush; Lin, Huijia; Sahai, Amit (2020). "Indistinguishability Obfuscation from Well-Founded Assumptions". Cryptology ePrint Archive. arXiv:2008.09317.
6. ^ a b Moran, Tal; Rosen, Alon (7 October 2013). "There is no Indistinguishability Obfuscation in Pessiland" (PDF). IACR Cryptology ePrint Archive.
7. ^ a b c Barak, Boaz; Goldreich, Oded; Impagliazzo, Russell; Rudich, Steven; Sahai, Amit; Vadhan, Salil; Yang, Ke (2012-05-03). "On the (im)possibility of obfuscating programs" (PDF). Journal of the ACM. 59 (2): 6:1–6:48. doi:10.1145/2160158.2160159. ISSN 0004-5411. S2CID 2409597.
8. ^ a b c Klarreich, Erica (2014-01-30). "Perfecting the Art of Sensible Nonsense". Quanta Magazine. Retrieved 2021-08-22.
9. ^ a b Goldwasser, Shafi; Rothblum, Guy N. (2007). Vadhan, Salil P. (ed.). "On Best-Possible Obfuscation". Theory of Cryptography. Lecture Notes in Computer Science. Berlin, Heidelberg: Springer. 4392: 194–213. doi:10.1007/978-3-540-70936-7_11. hdl:1721.1/129413. ISBN 978-3-540-70936-7.
10. ^ a b Sanjam Garg; Craig Gentry; Shai Halevi; Mariana Raykova; Amit Sahai; Brent Waters (2013). "Candidate Indistinguishability Obfuscation and Functional Encryption for all Circuits". Focs 2013. IEEE: 40–49. CiteSeerX 10.1.1.672.1968. doi:10.1109/FOCS.2013.13. ISBN 978-0-7695-5135-7. S2CID 15703414.
11. ^ Applebaum, B; Ishai, Y; Kushilevitz, E (2006). "Cryptography in NC0" (PDF). SIAM Journal on Computing. 36 (4): 845–888. doi:10.1137/S0097539705446950.
12. ^ Banescu, Sebastian; Ochoa, Martín; Kunze, Nils; Pretschner, Alexander (2015). Piessens, Frank; Caballero, Juan; Bielova, Nataliia (eds.). "Idea: Benchmarking Indistinguishability Obfuscation – A Candidate Implementation" (PDF). Engineering Secure Software and Systems. Lecture Notes in Computer Science. Cham: Springer International Publishing. 8978: 149–156. doi:10.1007/978-3-319-15618-7_12. ISBN 978-3-319-15618-7.
13. ^ Impagliazzo, Russell (19–22 June 1995). "A personal view of average-case complexity". Proceedings of Structure in Complexity Theory. Tenth Annual IEEE Conference: 134–147. doi:10.1109/SCT.1995.514853. ISBN 0-8186-7052-5. S2CID 2154064. Retrieved 27 July 2022.
14. ^ Bitansky, Nir; Nishimaki, Ryo; Passelègue, Alain; Wichs, Daniel (30 August 2017). "From Cryptomania to Obfustopia through Secret-Key Functional Encryption" (PDF). IACR Cryptology ePrint Archive.
15. ^ Garg, Sanjam; Pandey, Omkant; Srinivasan, Akshayaram; Zhandry, Mark (2017). Coron, Jean-Sébastien; Nielsen, Jesper Buus (eds.). "Breaking the Sub-Exponential Barrier in Obfustopia". Advances in Cryptology – EUROCRYPT 2017. Lecture Notes in Computer Science. Cham: Springer International Publishing. 10212: 156–181. doi:10.1007/978-3-319-56617-7_6. ISBN 978-3-319-56617-7.
16. ^ Koppula, Venkata; Lewko, Allison Bishop; Waters, Brent (2015-06-14). "Indistinguishability Obfuscation for Turing Machines with Unbounded Memory" (PDF). Proceedings of the Forty-Seventh Annual ACM Symposium on Theory of Computing. STOC '15. Portland, Oregon, USA: Association for Computing Machinery: 419–428. doi:10.1145/2746539.2746614. ISBN 978-1-4503-3536-2. S2CID 1368494.
17. ^ Ananth, Prabhanjan; Jain, Abhishek; Sahai, Amit (2017). Katz, Jonathan; Shacham, Hovav (eds.). "Indistinguishability Obfuscation for Turing Machines: Constant Overhead and Amortization" (PDF). Advances in Cryptology – CRYPTO 2017. Lecture Notes in Computer Science. Cham: Springer International Publishing. 10402: 252–279. doi:10.1007/978-3-319-63715-0_9. ISBN 978-3-319-63715-0.
18. Sahai, Amit; Waters, Brent (2013). "How to Use Indistinguishability Obfuscation: Deniable Encryption, and More". Cryptology ePrint Archive.
19. ^ Bitansky, Nir; Paneth, Omer; Rosen, Alon (October 2015). "On the Cryptographic Hardness of Finding a Nash Equilibrium". 2015 IEEE 56th Annual Symposium on Foundations of Computer Science: 1480–1498. doi:10.1109/FOCS.2015.94. ISBN 978-1-4673-8191-8. S2CID 217890992.
20. ^ Asharov, Gilad; Segev, Gil (2015). "Limits on the Power of Indistinguishability Obfuscation and Functional Encryption". Cryptology ePrint Archive.