Probabilistic encryption: Difference between revisions
imported>IrisChronomia →Security: changed pronouns referring to a hypothetical person to "they" |
imported>Monkbot |
||
| Line 1: | Line 1: | ||
{{Short description|Use of randomness in key code generation}} | {{Short description|Use of randomness in key code generation}} | ||
'''Probabilistic encryption''' is the use of [[randomness]] in an [[encryption]] algorithm, so that when encrypting the same message several times it will, in general, yield different [[ciphertext]]s. The term "probabilistic encryption" is typically used in reference to [[public key cryptography|public key]] encryption algorithms; however various [[symmetric key encryption]] algorithms achieve a similar property (e.g., [[block ciphers]] when used in a chaining mode such as [[Cipher block chaining|CBC]]), and stream ciphers such as Freestyle<ref>{{Cite journal|last=Puthuparambil|first=Arun Babu|last2=Thomas|first2=Jithin Jose|date=2019-12-01|title=Freestyle, a randomized version of ChaCha for resisting offline brute-force and dictionary attacks|journal=Journal of Information Security and Applications|language=en|volume=49| | '''Probabilistic encryption''' is the use of [[randomness]] in an [[encryption]] algorithm, so that when encrypting the same message several times it will, in general, yield different [[ciphertext]]s. The term "probabilistic encryption" is typically used in reference to [[public key cryptography|public key]] encryption algorithms; however various [[symmetric key encryption]] algorithms achieve a similar property (e.g., [[block ciphers]] when used in a chaining mode such as [[Cipher block chaining|CBC]]), and stream ciphers such as Freestyle<ref>{{Cite journal|last=Puthuparambil|first=Arun Babu|last2=Thomas|first2=Jithin Jose|date=2019-12-01|title=Freestyle, a randomized version of ChaCha for resisting offline brute-force and dictionary attacks|journal=Journal of Information Security and Applications|language=en|volume=49|article-number=102396|doi=10.1016/j.jisa.2019.102396|arxiv=1802.03201|issn=2214-2126}}</ref> which are inherently random. To be [[semantic security|semantically secure]], that is, to hide even partial information about the [[plaintext]], an encryption algorithm must be [[randomized algorithm|probabilistic]]. | ||
== History == | == History == | ||
The first provably-secure probabilistic public-key encryption scheme was proposed by [[Shafi Goldwasser]] and [[Silvio Micali]], based on the hardness of the [[quadratic residuosity problem]] and had a message expansion factor equal to the public key size. More efficient probabilistic encryption algorithms include [[ElGamal encryption|Elgamal]], [[Paillier]], and various constructions under the [[random oracle model]], including OAEP. | The first provably-secure probabilistic public-key encryption scheme was proposed by [[Shafi Goldwasser]] and [[Silvio Micali]], based on the hardness of the [[quadratic residuosity problem]] and had a message expansion factor equal to the public key size. More efficient probabilistic encryption algorithms include [[ElGamal encryption|Elgamal]], [[Paillier]], and various constructions under the [[random oracle model]], including [[optimal asymmetric encryption padding]] (OAEP). | ||
== Security == | == Security == | ||
| Line 10: | Line 10: | ||
Probabilistic encryption is particularly important when using [[public key cryptography]]. Suppose that the [[Adversary (cryptography)|adversary]] observes a ciphertext, and suspects that the plaintext is either "YES" or "NO", or has a hunch that the plaintext might be "ATTACK AT CALAIS". When a [[deterministic encryption]] algorithm is used, the adversary can simply try encrypting each of their guesses under the recipient's public key, and compare each result to the target ciphertext. To combat this attack, public key encryption schemes must incorporate an element of randomness, ensuring that each plaintext maps into one of a large number of possible ciphertexts. | Probabilistic encryption is particularly important when using [[public key cryptography]]. Suppose that the [[Adversary (cryptography)|adversary]] observes a ciphertext, and suspects that the plaintext is either "YES" or "NO", or has a hunch that the plaintext might be "ATTACK AT CALAIS". When a [[deterministic encryption]] algorithm is used, the adversary can simply try encrypting each of their guesses under the recipient's public key, and compare each result to the target ciphertext. To combat this attack, public key encryption schemes must incorporate an element of randomness, ensuring that each plaintext maps into one of a large number of possible ciphertexts. | ||
An intuitive approach to converting a deterministic encryption scheme into a probabilistic one is to simply pad the plaintext with a random string before encrypting with the [[deterministic algorithm]]. Conversely, decryption involves applying a deterministic algorithm and ignoring the random padding. However, early schemes which applied this naive approach were broken due to limitations in some deterministic encryption schemes. Techniques such as [[Optimal Asymmetric Encryption Padding]] (OAEP) integrate random padding in a manner that is secure using any [[trapdoor permutation]]. | An intuitive approach to converting a deterministic encryption scheme into a probabilistic one is to simply pad the plaintext with a random string before encrypting with the [[deterministic algorithm]]. Conversely, decryption involves applying a deterministic algorithm and ignoring the random padding. However, early schemes which applied this naive approach were broken due to limitations in some deterministic encryption schemes. Techniques such as [[Optimal Asymmetric Encryption Padding|optimal asymmetric encryption padding]] (OAEP) integrate random padding in a manner that is secure using any [[trapdoor permutation]]. | ||
== Examples == | == Examples == | ||
| Line 17: | Line 17: | ||
* ''x'' - ''single bit'' plaintext | * ''x'' - ''single bit'' plaintext | ||
* ''f'' - | * ''f'' - trapdoor permutation (deterministic encryption algorithm) | ||
* ''b'' - [[hard core predicate]] of ''f'' | * ''b'' - [[hard core predicate]] of ''f'' | ||
* ''r'' - random string | * ''r'' - random string | ||
| Line 34: | Line 34: | ||
* ''x'' - plaintext | * ''x'' - plaintext | ||
* ''f'' - | * ''f'' - trapdoor permutation (deterministic encryption algorithm) | ||
* ''h'' - [[random oracle]] (typically implemented using a publicly specified [[cryptographic hash function|hash function]]) | * ''h'' - [[random oracle]] (typically implemented using a publicly specified [[cryptographic hash function|hash function]]) | ||
* ''r'' - random string | * ''r'' - random string | ||
Latest revision as of 20:18, 4 October 2025
Template:Short description Probabilistic encryption is the use of randomness in an encryption algorithm, so that when encrypting the same message several times it will, in general, yield different ciphertexts. The term "probabilistic encryption" is typically used in reference to public key encryption algorithms; however various symmetric key encryption algorithms achieve a similar property (e.g., block ciphers when used in a chaining mode such as CBC), and stream ciphers such as Freestyle[1] which are inherently random. To be semantically secure, that is, to hide even partial information about the plaintext, an encryption algorithm must be probabilistic.
History
The first provably-secure probabilistic public-key encryption scheme was proposed by Shafi Goldwasser and Silvio Micali, based on the hardness of the quadratic residuosity problem and had a message expansion factor equal to the public key size. More efficient probabilistic encryption algorithms include Elgamal, Paillier, and various constructions under the random oracle model, including optimal asymmetric encryption padding (OAEP).
Security
Probabilistic encryption is particularly important when using public key cryptography. Suppose that the adversary observes a ciphertext, and suspects that the plaintext is either "YES" or "NO", or has a hunch that the plaintext might be "ATTACK AT CALAIS". When a deterministic encryption algorithm is used, the adversary can simply try encrypting each of their guesses under the recipient's public key, and compare each result to the target ciphertext. To combat this attack, public key encryption schemes must incorporate an element of randomness, ensuring that each plaintext maps into one of a large number of possible ciphertexts.
An intuitive approach to converting a deterministic encryption scheme into a probabilistic one is to simply pad the plaintext with a random string before encrypting with the deterministic algorithm. Conversely, decryption involves applying a deterministic algorithm and ignoring the random padding. However, early schemes which applied this naive approach were broken due to limitations in some deterministic encryption schemes. Techniques such as optimal asymmetric encryption padding (OAEP) integrate random padding in a manner that is secure using any trapdoor permutation.
Examples
Example of probabilistic encryption using any trapdoor permutation:
- x - single bit plaintext
- f - trapdoor permutation (deterministic encryption algorithm)
- b - hard core predicate of f
- r - random string
This is inefficient because only a single bit is encrypted. In other words, the message expansion factor is equal to the public key size.
Example of probabilistic encryption in the random oracle model:
- x - plaintext
- f - trapdoor permutation (deterministic encryption algorithm)
- h - random oracle (typically implemented using a publicly specified hash function)
- r - random string
See also
References
<templatestyles src="Reflist/styles.css" />
- ↑ Script error: No such module "Citation/CS1".
Script error: No such module "Check for unknown parameters".
External links
- Shafi Goldwasser and Silvio Micali, Probabilistic Encryption, Special issue of Journal of Computer and Systems Sciences, Vol. 28, No. 2, pages 270-299, April 1984
- Freestyle, a randomized version of ChaCha for resisting offline brute-force and dictionary attacks [1].