Loading [MathJax]/jax/output/HTML-CSS/jax.js
Skip to main content
Library homepage
 

Text Color

Text Size

 

Margin Size

 

Font Type

Enable Dyslexic Font
Engineering LibreTexts

15.1: Security Definitions

( \newcommand{\kernel}{\mathrm{null}\,}\)

We now modify the definition of CPA security to fit the setting of public-key encryption. As before, the adversary calls a CHALLENGE subroutine with two plaintexts the difference between the two libraries is which plaintext is actually encrypted. Of course, the encryption operation now takes the public key.

Then the biggest change is that we would like to make the public key public. In other words, the calling program should have a way to learn the public key (otherwise the library cannot model a situation where the public key is known to the adversary). To do this, we simply add another subroutine that returns the public key.

Definition 15.1

Let Σ be a public-key encryption scheme. Then Σ is secure against chosen-plaintext at-tacks (CPA secure) if LΣpk-cpa-LLΣpk-cpa-R, where:

fig-ch01_patchfile_01.jpg
Figure 15.1.1: Copy and Paste Caption here. (Copyright; author via source)

Pseudorandom Ciphertexts

We can modify/adapt the definition of pseudorandom ciphertexts to public-key encryption in a similar way:

Definition 15.2

Let Σ be a public-key encryption scheme. Then Σ has pseudorandom ciphertexts in the presence of chosen-plaintext attacks (CPA$ security) if LΣpk-cpa$-real LΣpk-cpa$-rand , where:

fig-ch01_patchfile_01.jpg
Figure 15.1.1: Copy and Paste Caption here. (Copyright; author via source)

As in the symmetric-key setting, CPA$ security (for public-key encryption) implies CPA security:

Claim 15.3

Let Σ be a public-key encryption scheme. If has CPA$ security, then Σ has CPA security.

The proof is extremely similar to the proof of the analogous statement for symmetrickey encryption (Theorem 7.3), and is left as an exercise.


This page titled 15.1: Security Definitions is shared under a CC BY-NC-SA 4.0 license and was authored, remixed, and/or curated by Mike Rosulek (Open Oregon State) .

Support Center

How can we help?