WEBVTT - This file was automatically generated by VIMEO

0
00:00:09.500 --> 00:00:10.900
Welcome to section 4.

1
00:00:11.800 --> 00:00:14.600
Section 4 is the first section of

2
00:00:14.600 --> 00:00:17.800
 our in-depth study of the famous public

3
00:00:17.800 --> 00:00:21.000
 key cryptography in this section. We'll

4
00:00:20.100 --> 00:00:23.300
 see the most common algorithms and

5
00:00:23.300 --> 00:00:25.800
 Protocols of public key cryptography.

6
00:00:27.900 --> 00:00:30.200
In these first video, we will look

7
00:00:30.200 --> 00:00:34.100
 at the picture of public key cryptography and

8
00:00:33.100 --> 00:00:36.700
 start to understand. What is its

9
00:00:36.700 --> 00:00:39.100
 value compared to symmetric key cryptography.

10
00:00:40.300 --> 00:00:43.600
Will revisit the Symmetry key methods we saw

11
00:00:43.600 --> 00:00:46.800
 in sections 2 and 3 and see their counterparts

12
00:00:46.800 --> 00:00:48.000
 in public key cryptography.

13
00:00:49.100 --> 00:00:49.900
So let's get started.

14
00:00:52.800 --> 00:00:55.700
The invention of public key cryptography is

15
00:00:55.700 --> 00:00:58.900
 related to a paper named new directions

16
00:00:58.900 --> 00:01:00.000
 in cryptography.

17
00:01:01.100 --> 00:01:06.500
These people was published by the two cryptographers Whitefield

18
00:01:05.500 --> 00:01:09.200
 TV and Martin Hellman in

19
00:01:08.200 --> 00:01:10.100
 1976.

20
00:01:11.400 --> 00:01:14.400
These people introduced the concept of public key

21
00:01:14.400 --> 00:01:14.900
 cryptography.

22
00:01:15.700 --> 00:01:18.100
Defend Herman described how we can

23
00:01:18.100 --> 00:01:21.200
 use one-way functions to construct the

24
00:01:21.200 --> 00:01:23.700
 methods and algorithms of public key cryptography.

25
00:01:25.100 --> 00:01:28.100
One Way functions are functions that are easy to

26
00:01:28.100 --> 00:01:30.300
 apply and hard to invert.

27
00:01:31.200 --> 00:01:34.100
Unless you have the key bound to that one-way function.

28
00:01:35.300 --> 00:01:38.300
No worries, if the concept of four way

29
00:01:38.300 --> 00:01:41.000
 function still seems abstract or clear.

30
00:01:42.600 --> 00:01:45.100
We'll see it in more detail in this video and in the

31
00:01:45.100 --> 00:01:45.700
 coming videos.

32
00:01:47.500 --> 00:01:50.800
Using this one-way functions different element

33
00:01:50.800 --> 00:01:54.400
 described how we can create encryption algorithms

34
00:01:53.400 --> 00:01:56.700
 that ensure data confidentiality.

35
00:01:57.600 --> 00:02:00.900
And digital signatures that ensure data

36
00:02:00.900 --> 00:02:03.200
 integrity and origin Authentication.

37
00:02:04.800 --> 00:02:07.900
Different element did not provide any concrete examples

38
00:02:07.900 --> 00:02:11.200
 of how we can create such encryption

39
00:02:10.200 --> 00:02:13.900
 or digital signature algorithms.

40
00:02:14.700 --> 00:02:16.800
The only describe the high-level concept.

41
00:02:18.200 --> 00:02:22.300
In the next years after this paper many cryptographers

42
00:02:21.300 --> 00:02:24.800
 will propose actual constructions

43
00:02:24.800 --> 00:02:27.500
 of public key encryption and digital

44
00:02:27.500 --> 00:02:28.800
 signature algorithms.

45
00:02:30.100 --> 00:02:33.600
However, different element proposed both the

46
00:02:33.600 --> 00:02:37.200
 idea and actual contract construction for another

47
00:02:36.200 --> 00:02:37.900
 functionality.

48
00:02:38.700 --> 00:02:39.400
key agreement

49
00:02:40.600 --> 00:02:43.700
key agreement is a protocol that allows two

50
00:02:43.700 --> 00:02:45.800
 parties to construct a common key.

51
00:02:47.400 --> 00:02:51.100
Let's start by seeing how we can have encryption using

52
00:02:50.100 --> 00:02:52.300
 public key cryptography.

53
00:02:53.500 --> 00:02:56.400
first remember how symmetric key encryption

54
00:02:56.400 --> 00:02:56.600
 works

55
00:02:57.500 --> 00:03:00.400
to parties I listen Bob have to

56
00:03:00.400 --> 00:03:02.400
 obtain a common secret key k

57
00:03:03.100 --> 00:03:06.600
that is then used to encrypt plain texts and decrypt

58
00:03:06.600 --> 00:03:07.400
 cycle texts.

59
00:03:08.300 --> 00:03:11.800
One of these parties yearbook generates this

60
00:03:11.800 --> 00:03:14.600
 key and transfer it to Alice using

61
00:03:14.600 --> 00:03:18.400
 some authenticated and confidential Channel.

62
00:03:19.700 --> 00:03:23.300
Confidentiality requires that no other parties should

63
00:03:22.300 --> 00:03:25.200
 see the content of this communication.

64
00:03:26.400 --> 00:03:29.600
And authentication means that Bob is sure

65
00:03:29.600 --> 00:03:32.100
 to transmit the key to Alice and not to an

66
00:03:32.100 --> 00:03:35.500
 adversary and similarly. Alice should be sure that this key

67
00:03:35.500 --> 00:03:38.400
 comes from Bob and not from adversary.

68
00:03:40.700 --> 00:03:44.800
When it comes to public key encryption pubgenerates

69
00:03:43.800 --> 00:03:45.600
 a pair of keys.

70
00:03:46.600 --> 00:03:47.600
the first key

71
00:03:48.600 --> 00:03:52.000
called public key PK and the

72
00:03:51.100 --> 00:03:54.500
 second key called secret key

73
00:03:54.500 --> 00:03:55.500
 SK.

74
00:03:57.900 --> 00:04:00.400
Bobs and PK to Alice and keeps Escape

75
00:04:01.500 --> 00:04:04.400
when Alice wants to send a message to Bob using

76
00:04:04.400 --> 00:04:06.000
 unsecure Channel.

77
00:04:07.100 --> 00:04:10.500
She uses PK to encrypt the message.

78
00:04:11.400 --> 00:04:14.400
And send it ciphertext to Bob that

79
00:04:14.400 --> 00:04:17.300
 uses ski to decrypted back to the

80
00:04:17.300 --> 00:04:17.900
 plaintext.

81
00:04:19.200 --> 00:04:22.500
The adversary that intercepts the ciphertext cannot retrieve the

82
00:04:22.500 --> 00:04:25.900
 original plaintext. That's exactly the same guarantee as

83
00:04:25.900 --> 00:04:27.600
 for symmetric key encryption.

84
00:04:29.300 --> 00:04:33.000
There then two major differences with symmetric encryption.

85
00:04:34.100 --> 00:04:37.400
First is the fact that there are two keys one used for

86
00:04:37.400 --> 00:04:39.800
 encryption and the other is for decryption.

87
00:04:40.600 --> 00:04:44.800
And the second difference which is very important

88
00:04:43.800 --> 00:04:46.400
 here is related

89
00:04:46.400 --> 00:04:47.700
 to the key transfer.

90
00:04:48.800 --> 00:04:51.300
Alison Bob needs only to

91
00:04:51.300 --> 00:04:54.300
 have an authenticated channel for the

92
00:04:54.300 --> 00:04:57.400
 key transfer, but the transfer of the PK.

93
00:04:59.300 --> 00:05:02.700
So public cryptography allows a less

94
00:05:02.700 --> 00:05:06.400
 constraining setting for the key transfer compared

95
00:05:05.400 --> 00:05:07.400
 to symmetric key.

96
00:05:08.200 --> 00:05:11.200
Cryptography where Alice and Bob has to

97
00:05:11.200 --> 00:05:14.200
 use an authenticated and confidential Channel.

98
00:05:15.800 --> 00:05:17.500
So for symmetric key.

99
00:05:18.500 --> 00:05:21.400
Alice and Bob has maybe to meet directly

100
00:05:21.400 --> 00:05:24.500
 and get the key while ensuring that

101
00:05:24.500 --> 00:05:25.800
 no one else is listening.

102
00:05:27.200 --> 00:05:28.500
while for public key

103
00:05:29.100 --> 00:05:32.300
Alice has only to be sure that the PK of Bob

104
00:05:32.300 --> 00:05:33.500
 comes really from

105
00:05:34.500 --> 00:05:37.700
she doesn't need to meet him to get that she can

106
00:05:37.700 --> 00:05:40.800
 retrieve that key from his website or even

107
00:05:40.800 --> 00:05:43.900
 from another person that she

108
00:05:43.900 --> 00:05:46.200
 trusts that tells her about the key of

109
00:05:46.200 --> 00:05:46.600
 Pop.

110
00:05:48.200 --> 00:05:48.400
so

111
00:05:49.400 --> 00:05:52.200
For symmetric key. Alice has also to

112
00:05:52.200 --> 00:05:55.700
 store the key in a secure

113
00:05:55.700 --> 00:05:55.800
 location.

114
00:05:56.800 --> 00:05:59.800
Because losing that key will break the confidentiality of

115
00:05:59.800 --> 00:06:02.200
 all the ciphertexts encrypted with

116
00:06:02.200 --> 00:06:02.900
 that key.

117
00:06:04.200 --> 00:06:07.600
Well for public key. Alice does not even need to store it locally.

118
00:06:08.700 --> 00:06:11.600
She just need to get it from where Bob

119
00:06:11.600 --> 00:06:12.300
 publish it.

120
00:06:14.100 --> 00:06:17.200
Digital signatures are the counterpart of

121
00:06:17.200 --> 00:06:20.700
 message authentication codes Max in the

122
00:06:20.700 --> 00:06:22.400
 public key cryptography.

123
00:06:23.500 --> 00:06:25.300
Let's review briefly Mac.

124
00:06:26.200 --> 00:06:29.500
In Mac Alice and Bob have a common key.

125
00:06:30.800 --> 00:06:33.600
Alice would like to prove to pop that her

126
00:06:33.600 --> 00:06:36.100
 message was not modified and comes from her.

127
00:06:37.200 --> 00:06:40.500
So she computes using the key k a code

128
00:06:40.500 --> 00:06:43.000
 C that she appended to her message X.

129
00:06:44.300 --> 00:06:47.900
Bob recomputes the code C on Alice's

130
00:06:47.900 --> 00:06:48.100
 message

131
00:06:48.700 --> 00:06:51.400
using the key and checks if it matches

132
00:06:51.400 --> 00:06:53.000
 with the code that early set.

133
00:06:54.200 --> 00:06:57.800
When it comes to digital signatures Alice has

134
00:06:57.800 --> 00:07:00.400
 a pair of public key and secret key.

135
00:07:01.500 --> 00:07:04.500
She uses her secret key to compute a signature

136
00:07:04.500 --> 00:07:07.200
 as that. She opens it to her

137
00:07:07.200 --> 00:07:07.800
 message X.

138
00:07:08.800 --> 00:07:10.700
And send them to Bob.

139
00:07:11.900 --> 00:07:14.500
Bob uses Alice's public key

140
00:07:15.200 --> 00:07:18.600
to verify that the pair of message and signature is

141
00:07:18.600 --> 00:07:19.200
 valid.

142
00:07:21.200 --> 00:07:25.300
You might have noticed that for encryption at least

143
00:07:24.300 --> 00:07:27.200
 uses Bob's public key to

144
00:07:27.200 --> 00:07:30.100
 encrypt the message that only Bob can decrypt using his

145
00:07:30.100 --> 00:07:31.100
 secret key.

146
00:07:32.100 --> 00:07:35.700
In signatures at least uses her own secret key

147
00:07:35.700 --> 00:07:39.300
 to sign a message and Bob uses Alice's

148
00:07:38.300 --> 00:07:41.300
 public key to verify that the message

149
00:07:41.300 --> 00:07:43.800
 was not modified and is authenticated.

150
00:07:45.400 --> 00:07:48.500
Alice could not have used Bob's secret

151
00:07:48.500 --> 00:07:51.300
 key because only Bob has access to

152
00:07:51.300 --> 00:07:51.900
 that key.

153
00:07:53.300 --> 00:07:56.200
Also, she could not do the

154
00:07:56.200 --> 00:07:59.500
 other way and use her own public key

155
00:07:59.500 --> 00:08:02.800
 because in that case anyone can force

156
00:08:02.800 --> 00:08:05.600
 signature because anyone can

157
00:08:05.600 --> 00:08:08.000
 do that because her public key is public.

158
00:08:08.600 --> 00:08:10.300
There is also a last remark.

159
00:08:10.900 --> 00:08:12.100
similar to encryption

160
00:08:13.100 --> 00:08:14.500
For Mac.

161
00:08:15.200 --> 00:08:18.500
The two parties need an authenticated and

162
00:08:18.500 --> 00:08:21.100
 confidential channel for the key transfer.

163
00:08:21.900 --> 00:08:24.700
But for digital signatures only in

164
00:08:24.700 --> 00:08:27.600
 authenticated channel is needed to transfer

165
00:08:27.600 --> 00:08:28.200
 the public key.

166
00:08:29.800 --> 00:08:32.300
Okay, let's now move to the

167
00:08:32.300 --> 00:08:35.900
 last functionality that was described in different

168
00:08:35.900 --> 00:08:36.600
 element paper.

169
00:08:37.800 --> 00:08:39.200
Which is key agreement.

170
00:08:40.200 --> 00:08:43.600
To understand key agreement. Let's start from the key

171
00:08:43.600 --> 00:08:46.600
 transfer that we used so far in the

172
00:08:46.600 --> 00:08:47.800
 symmetric key cryptography.

173
00:08:48.900 --> 00:08:51.400
One party is responsible of generating the

174
00:08:51.400 --> 00:08:55.200
 key then transmitted to the second party

175
00:08:54.200 --> 00:08:57.900
 using an authenticated and confidential Channel.

176
00:09:00.100 --> 00:09:03.800
Key agreement allows two users to construct together

177
00:09:03.800 --> 00:09:05.000
 a common key.

178
00:09:05.700 --> 00:09:08.800
In order to construct this key the parties run

179
00:09:08.800 --> 00:09:11.200
 a protocol and exchange some data.

180
00:09:12.200 --> 00:09:15.800
The channel to exchange this data has to only

181
00:09:15.800 --> 00:09:19.600
 be authenticated no confidentiality requirements

182
00:09:19.600 --> 00:09:22.400
 like in the symmetric key

183
00:09:22.400 --> 00:09:23.500
 cryptography.

184
00:09:25.300 --> 00:09:28.900
At the end of the protocol I listened Bob obtained the

185
00:09:28.900 --> 00:09:29.900
 same TK.

186
00:09:31.200 --> 00:09:34.700
And adversary that intercepted all their exchanges cannot

187
00:09:34.700 --> 00:09:35.300
 retrieve.

188
00:09:37.700 --> 00:09:40.300
You might be wondering why are the two

189
00:09:40.300 --> 00:09:43.200
 parties constructed a key? We have seen in the

190
00:09:43.200 --> 00:09:46.700
 last two slides we can encrypt and sign messages using

191
00:09:46.700 --> 00:09:49.500
 the pair of public key and

192
00:09:49.500 --> 00:09:49.900
 secret key.

193
00:09:51.200 --> 00:09:55.200
When key agreement is a very interesting

194
00:09:54.200 --> 00:09:58.000
 if we would like to combine public

195
00:09:57.400 --> 00:10:00.000
 key and symmetric key.

196
00:10:00.600 --> 00:10:04.000
And this is very common in real world applications to

197
00:10:03.300 --> 00:10:06.800
 use public key cryptography to

198
00:10:06.800 --> 00:10:09.700
 agree on a key. And

199
00:10:09.700 --> 00:10:12.400
 then we use that key to switch to

200
00:10:12.400 --> 00:10:14.100
 symmetric key description.

201
00:10:15.400 --> 00:10:19.700
The rationale behind this is that symmetric key

202
00:10:18.700 --> 00:10:21.500
 cryptography is much faster

203
00:10:21.500 --> 00:10:23.200
 than public key cryptography.

204
00:10:24.200 --> 00:10:27.800
So we use this slow public key cryptography to agree

205
00:10:27.800 --> 00:10:30.600
 on the key and then we switch to more efficient

206
00:10:30.600 --> 00:10:33.000
 symmetry key scripture.

207
00:10:34.900 --> 00:10:37.800
On this video. We introduced the high

208
00:10:37.800 --> 00:10:40.400
 level ideas public key cryptography.

209
00:10:41.200 --> 00:10:44.800
We saw how we can have counterparts of symmetry

210
00:10:44.800 --> 00:10:47.300
 encryption and Max which are the

211
00:10:47.300 --> 00:10:50.400
 public encryption and digital signatures.

212
00:10:51.600 --> 00:10:54.500
We saw that for this counterparts the key transfer

213
00:10:54.500 --> 00:10:56.700
 requires less constraining Channel.

214
00:10:57.500 --> 00:11:01.400
That makes public key cryptography particularly powerful

215
00:11:00.400 --> 00:11:03.400
 to be used in many real

216
00:11:03.400 --> 00:11:06.700
 world applications. We are having confidential channels is

217
00:11:06.700 --> 00:11:07.300
 not possible.

218
00:11:08.800 --> 00:11:12.200
In the next videos, we will see the actual constructions.

219
00:11:13.100 --> 00:11:16.600
And you will start with the key agreement that different element

220
00:11:16.600 --> 00:11:18.100
 proposed in their publication.

221
00:11:19.100 --> 00:11:20.800
So see you in the next video.
