Scribed by Ian Haken
Summary
The encryption scheme we saw last time, based on pseudorandom functions, works and is CPAsecure, but it is not used in practice. A disadvantage of the scheme is that the length of the encryption is twice the length of the message being sent.
Today we see the “counter mode” generalization of that scheme, which has considerably smaller overhead for long messages, and see that this preserves CPAsecurity.
We then give the definition of pseudorandom permutation, which is a rigorous formalization of the notion of block cipher from applied cryptography, and see two ways of using block ciphers to perform encryption. One is totally insecure (ECB), the other (CBC) achieves CPA security.
1. The Randomized Counter Mode
Recall that a pseudorandom function is a function which looks approximately like a random function . With the encryption method from the previous lecture (in which the ciphertext is a random followed by ) the encryption of a message is twice as long as the original message. We now define an encryption method which continues to use a pseudorandom function, but whose ciphertext overhead is marginal.
Suppose we have a pseudorandom function . We describe an encryption scheme that works for messages of variable length. We assume without loss of generality that the length of the message is a multiple of , and we write a plaintext of length as , a sequence of blocks of length .
(When is a binary string in and is an integer, means the binary representation of the sum mod of (seen as an integer) and .)
Observe that the ciphertext length is which is a negligable overhead when .
Theorem 1 Suppose is a secure pseudorandom function; then, when used to encrypt messages of length , the above scheme is CPA secure.
Example 1 Consider the values which these variables might take in the transmission of a large (e.g. 4GB) file. If we let , , , , then we end up with an approximately CPA secure transmission.
Proof: Recall the proof from last time in which we defined , where is a truly random function. Given messages and a cryptanalytic algorithm , we considered:
We were able to show in the previous proof that , , and , thus showing that . Our proof will follow similarly.
We will first show that for any
hence showing and . Suppose for a contradiction that this is not the case, i.e. and where is of complexity such that
Define as a program which simulates . (Note that has complexity ). Noting that and , this program would be a counterexample to being secure.
Now we want to show that , , and such that the complexity of is ,
As in the previous proof, we consider the requests may make to the oracle . The returned values from the oracle would be , where ranges between and the number of requests to the oracle. Since has complexity limited by , we can assume . As before, if none of the overlap with (for ) then only sees a random stream of bits from the oracle. Otherwise, if for some , then can recover, and hence distinguish, and . Hence the probability of distinguishing is plus the probability of a collision.
Note that the th oracle request will have a collision with some iff . If we have then obviously there is a collision, and otherwise so so there is a collision with . If is outside this range, then there is no way a collision can occur. Since is chosen randomly from the space of , there is a probability that the th oracle request has a collision. Hence is an upper bound on the probability that there is a collision in at least one the oracle requests.
Combining these results, we see that , i.e.
◻
2. Pseudorandom Permutations
2.1. Some Motivation
Suppose the message stream has known messages, such as a protocol which always has a common header. For example, suppose Eve knows that Bob is sending an email to Alice, and that the first block of the message is the sender’s email. That is, suppose Eve knows that “bob@cs.berkeley.edu”. If Eve can insert or modify messages on the channel, then upon seeing the ciphertext she could then send to Alice the stream “bob@cs.berkeley.edu” “eve@cs.berkeley.edu” . The result is that the message received by Alice would appear to be sent from “eve@cs.berkeley.edu”, but remain otherwise unchanged.
2.2. Definition
Denote by the set of permutations .
Definition 2 A pair of functions , is a secure pseudorandom permutation if:
That is, to any algorithm that doesn’t know , the functions look like a random permutation and its inverse.
In applied cryptography literature, pseudorandom permutations are called block ciphers.
How do we construct pseudorandom permutations? There are a number of block cipher proposals, including the AES standard, that have been studied extensively and are considered safe for the time being. We shall prove later that any construction of pseudorandom functions can be turned into a construction of pseudorandom permutations; also, every construction of pseudorandom generators can be turned into a pseudorandom function, and every oneway function can be used to construct a pseudorandom generator. Ultimately, this will mean that it is possible to construct a block cipher whose security relies, for example, on the hardness of factoring random integers. Such a construction, however, would not be practical.
3. Encryption Using Pseudorandom Permutations
Here are two ways of using Pseudorandom Functions and Permutations to perform encryption. Both are used in practice.
3.1. ECB Mode
The Electronic CodeBook mode of encryption works as follows
Exercise 1 Show that ECB is messageindistinguishable for onetime encryption but not for two encryptions.
3.2. CBC Mode
In its simplest instantiation the Cipher BlockChaining mode works as follows:
 : pick a random string , output

Note that this similar to (but a bit different from) the scheme based on pseudorandom functions that we saw last time. In CBC, we take advantage of the fact that is now a permutation that is efficiently invertible given the secret key, and so we are allowed to put the inside the computation of .
There is a generalization in which one can use the same random string to send several messages. (It requires synchronization and state information.)
Exercise 2 This mode achieves CPA security.
Note that CBC overcomes the above problem in which Eve knows a particular block of the message being sent, for if Eve modified in the encryption that Bob was sending to Alice (as in the example above) then the change would be noticeable because would not decrypt correctly.