WEBVTT - This file was automatically generated by VIMEO

0
00:00:18.400 --> 00:00:22.200
Hello everyone in this lesson. We will talk about SSL and

1
00:00:22.200 --> 00:00:24.800
 Kelly's protocols and Telus handshake.

2
00:00:26.200 --> 00:00:29.300
Let us talk about HTTP protocol a

3
00:00:29.300 --> 00:00:29.500
 little bit.

4
00:00:30.400 --> 00:00:33.500
The HTTP protocol hypertext transfer

5
00:00:33.500 --> 00:00:36.600
 protocol and TCP transmission control

6
00:00:36.600 --> 00:00:39.100
 protocol R2 separate protocols that

7
00:00:39.100 --> 00:00:41.700
 work together to transfer data over the internet.

8
00:00:42.500 --> 00:00:45.300
So the HTTP is an application layer

9
00:00:45.300 --> 00:00:48.400
 protocol. As you know, that is used to transfer data

10
00:00:48.400 --> 00:00:51.400
 in the form of web pages and other types of files.

11
00:00:52.100 --> 00:00:56.000
It is responsible for formatting and structuring the

12
00:00:55.400 --> 00:00:58.200
 data that is sent and received between

13
00:00:58.200 --> 00:01:01.800
 a client such as a web browser and a

14
00:01:01.800 --> 00:01:03.300
 server such as a web server.

15
00:01:04.200 --> 00:01:07.900
It defines a set of rules and commands such

16
00:01:07.900 --> 00:01:11.100
 as get and post it declined and

17
00:01:10.100 --> 00:01:14.000
 server and the server used to use

18
00:01:13.400 --> 00:01:15.700
 to communicate with each other.

19
00:01:16.700 --> 00:01:19.300
TCP on the other hand is a transport

20
00:01:19.300 --> 00:01:23.000
 layer protocol as you know, and it is responsible for

21
00:01:22.300 --> 00:01:26.100
 establishing at maintaining a

22
00:01:25.100 --> 00:01:28.500
 reliable connection between the

23
00:01:28.500 --> 00:01:29.800
 client and the server.

24
00:01:30.400 --> 00:01:33.900
It ensures that data is transferred

25
00:01:33.900 --> 00:01:37.400
 in an orderly and error-free manner

26
00:01:37.400 --> 00:01:40.800
 it established a connection between

27
00:01:40.800 --> 00:01:43.600
 the client and server and it also breaks down

28
00:01:43.600 --> 00:01:46.300
 data into small packets that

29
00:01:46.300 --> 00:01:47.700
 can be sent over the internet.

30
00:01:48.500 --> 00:01:51.400
It then reassemble the packets back into

31
00:01:51.400 --> 00:01:54.700
 the original data at the

32
00:01:54.700 --> 00:01:57.300
 other end and we know that

33
00:01:57.300 --> 00:02:00.400
 border transfer of HTTP data

34
00:02:00.400 --> 00:02:03.400
 a tcpc session must be

35
00:02:03.400 --> 00:02:05.700
 established in the transport layer.

36
00:02:06.400 --> 00:02:06.600
and

37
00:02:07.500 --> 00:02:11.700
so in terms of data transferring HTTP

38
00:02:10.700 --> 00:02:13.200
 runs on

39
00:02:13.200 --> 00:02:16.800
 top of TCP as you know, when I client

40
00:02:16.800 --> 00:02:19.700
 such as a web browser wants to

41
00:02:19.700 --> 00:02:22.700
 request a web page from a server. It

42
00:02:22.700 --> 00:02:25.300
 sends an HTTP request message to

43
00:02:25.300 --> 00:02:27.000
 the server using TCP.

44
00:02:27.600 --> 00:02:31.200
So when a client sends an HTTP

45
00:02:30.200 --> 00:02:33.600
 requests to a server, the

46
00:02:33.600 --> 00:02:36.800
 requisite message is first packaged as

47
00:02:36.800 --> 00:02:39.900
 a TCP segment by adding a

48
00:02:39.900 --> 00:02:42.300
 TCP heater trade and the resulting

49
00:02:42.300 --> 00:02:45.600
 packet is done sent to the destination server over

50
00:02:45.600 --> 00:02:48.400
 the Internet the server receives the packet and

51
00:02:48.400 --> 00:02:51.900
 the TCP layer removes the header

52
00:02:51.900 --> 00:02:54.200
 and delivers the request message to the

53
00:02:54.200 --> 00:02:57.700
 HTTP layer the HTTP layer than

54
00:02:57.700 --> 00:03:02.900
 processes the request and HTTP response

55
00:03:02.900 --> 00:03:06.000
 back to the client, which is again packaged as

56
00:03:05.300 --> 00:03:09.200
 a TCP segment by adding by

57
00:03:08.200 --> 00:03:12.200
 adding a TCP heater and sent

58
00:03:11.200 --> 00:03:12.800
 to the client.

59
00:03:13.400 --> 00:03:16.800
So the https, which means

60
00:03:16.800 --> 00:03:19.800
 HTTP secure is an

61
00:03:19.800 --> 00:03:22.600
 extension of the HTTP, as you

62
00:03:22.600 --> 00:03:25.700
 know, that adds an additional

63
00:03:25.700 --> 00:03:29.200
 layer of security by encrypting the

64
00:03:28.200 --> 00:03:31.200
 data that is sent and received between

65
00:03:31.200 --> 00:03:33.600
 a client and a server.

66
00:03:34.300 --> 00:03:37.600
Https uses the same commands and rules

67
00:03:37.600 --> 00:03:40.800
 as HTTP, but it adds an

68
00:03:40.800 --> 00:03:43.600
 extra layer of an extra

69
00:03:43.600 --> 00:03:46.600
 layer of security by encrypting the data

70
00:03:46.600 --> 00:03:49.400
 using a secure sockets layer.

71
00:03:50.100 --> 00:03:55.000
As you know the SSL or the TLs

72
00:03:53.200 --> 00:03:56.700
 the transport layer

73
00:03:56.700 --> 00:03:59.800
 security chart, but this

74
00:03:59.800 --> 00:04:03.500
 third bit is used to establish a secure

75
00:04:02.500 --> 00:04:05.900
 connection between the client and server

76
00:04:05.900 --> 00:04:08.800
 and it is used to encrypt and decrypt

77
00:04:08.800 --> 00:04:12.100
 and decrypt the data that is

78
00:04:11.100 --> 00:04:13.500
 sent and received.

79
00:04:14.100 --> 00:04:17.900
The process of establishing a secure connection using

80
00:04:17.900 --> 00:04:20.600
 https starts with

81
00:04:20.600 --> 00:04:23.700
 decline such as a web browser. You

82
00:04:23.700 --> 00:04:26.600
 can think of a web browser sanding

83
00:04:26.600 --> 00:04:29.700
 a request to the server the server

84
00:04:29.700 --> 00:04:33.700
 down response with a response that includes

85
00:04:32.700 --> 00:04:36.100
 a copy of its SSL

86
00:04:35.100 --> 00:04:39.200
 or TLS shortcut the client

87
00:04:39.200 --> 00:04:42.700
 verifies short, but by checking that it that

88
00:04:42.700 --> 00:04:46.000
 it was issued by a trusted third

89
00:04:45.300 --> 00:04:49.100
 you could order the and that it has

90
00:04:48.100 --> 00:04:51.400
 not expired if the

91
00:04:51.400 --> 00:04:54.800
 third but is valid and the client generates

92
00:04:54.800 --> 00:04:58.300
 addition key and Sans it

93
00:04:57.300 --> 00:05:00.800
 to the server encrypted with the service

94
00:05:00.800 --> 00:05:01.500
 publicly.

95
00:05:02.600 --> 00:05:05.200
And the servers then decrypts the

96
00:05:05.200 --> 00:05:08.500
 session key using its private

97
00:05:08.500 --> 00:05:11.400
 key and both the client at server use

98
00:05:11.400 --> 00:05:14.800
 the session key to encrypt and decrypt

99
00:05:14.800 --> 00:05:17.100
 all data sent between them.

100
00:05:18.200 --> 00:05:23.000
So when a client makes a request to an https site

101
00:05:22.800 --> 00:05:26.300
 the browser will first establish

102
00:05:25.300 --> 00:05:28.300
 a secure connection to the server.

103
00:05:28.800 --> 00:05:32.300
Once the connection is established. The browser

104
00:05:31.300 --> 00:05:34.300
 will send the request to the server

105
00:05:34.300 --> 00:05:37.000
 using the standard HTTP protocol.

106
00:05:38.100 --> 00:05:41.600
And the server will then process to request and

107
00:05:41.600 --> 00:05:44.800
 send the response back to the browser, which will

108
00:05:44.800 --> 00:05:47.700
 then decrypt the response and display to

109
00:05:47.700 --> 00:05:48.100
 the user.

110
00:05:49.200 --> 00:05:53.300
In comparison to http and https

111
00:05:52.300 --> 00:05:56.500
 provides several advantages

112
00:05:55.500 --> 00:05:59.100
 first, it encrypts

113
00:05:58.100 --> 00:06:01.400
 the data that is sand and received

114
00:06:01.400 --> 00:06:04.700
 which protects against used dropping and

115
00:06:04.700 --> 00:06:07.700
 tampering. This means that

116
00:06:07.700 --> 00:06:10.300
 anyone intercepting the data will

117
00:06:10.300 --> 00:06:12.400
 not be able to read or modify.

118
00:06:13.400 --> 00:06:16.300
Second it ordained case the server

119
00:06:16.300 --> 00:06:19.700
 which ensures that the client is communicating with

120
00:06:19.700 --> 00:06:21.100
 the intended server.

121
00:06:21.500 --> 00:06:23.500
and not an imposter

122
00:06:24.200 --> 00:06:27.900
So this prevents fishing attacks and man

123
00:06:27.900 --> 00:06:29.000
 in the middle attacks?

124
00:06:29.500 --> 00:06:29.900
finally

125
00:06:30.900 --> 00:06:33.600
It provides Integrity protection and

126
00:06:33.600 --> 00:06:36.600
 which ensures that the data

127
00:06:36.600 --> 00:06:40.300
 hasn't been tampered with within Transit.

128
00:06:41.100 --> 00:06:44.800
So in summary https is an

129
00:06:44.800 --> 00:06:47.700
 extension of HTTP that adds an

130
00:06:47.700 --> 00:06:50.500
 additional layer of security by encrypting the

131
00:06:50.500 --> 00:06:50.700
 data.

132
00:06:51.300 --> 00:06:54.200
Using SSL and SSL or

133
00:06:54.200 --> 00:06:57.900
 a TLS certificate https used

134
00:06:57.900 --> 00:07:01.100
 the same commands and rules as HTTP,

135
00:07:00.100 --> 00:07:03.200
 but it encrypts the data to

136
00:07:03.200 --> 00:07:07.000
 ensure privacy integrity and authentication

137
00:07:06.200 --> 00:07:07.800
 of the server.

138
00:07:08.400 --> 00:07:11.400
So the https is more secure than

139
00:07:11.400 --> 00:07:14.300
 HTTP protocol because it encrypts the

140
00:07:14.300 --> 00:07:17.600
 data authenticates the server and provides

141
00:07:17.600 --> 00:07:18.900
 Integrity protection.

142
00:07:19.800 --> 00:07:23.100
Now, let's look at the SSL

143
00:07:22.100 --> 00:07:24.900
 and TLS protocols.

144
00:07:26.400 --> 00:07:30.900
As you know the SSL which means secure circuits

145
00:07:30.900 --> 00:07:33.600
 layer and the TLs which means

146
00:07:33.600 --> 00:07:37.200
 transport layer security are both cryptographic

147
00:07:36.200 --> 00:07:39.800
 protocols and they provide

148
00:07:39.800 --> 00:07:42.100
 secure communication over networks. They are

149
00:07:42.100 --> 00:07:46.200
 used to secure a variety of application variety of

150
00:07:46.200 --> 00:07:49.700
 applications including web processing email

151
00:07:49.700 --> 00:07:52.800
 instant message of and

152
00:07:52.800 --> 00:07:55.600
 voice over IP. The main difference

153
00:07:55.600 --> 00:07:58.100
 between SSL and TLS is that

154
00:07:58.100 --> 00:08:01.200
 SSL is now considered to be

155
00:08:01.200 --> 00:08:04.800
 absolutely and insecure and

156
00:08:04.800 --> 00:08:07.600
 it has been replaced by TLS.

157
00:08:08.300 --> 00:08:11.800
In summary SSL and theories are

158
00:08:11.800 --> 00:08:15.100
 both cryptographic protocol that provides

159
00:08:14.100 --> 00:08:18.000
 secure communication over network. But ALS

160
00:08:17.200 --> 00:08:20.900
 is an updated and more secure

161
00:08:20.900 --> 00:08:23.800
 version of SSL. It is

162
00:08:23.800 --> 00:08:26.600
 recommended that to use the

163
00:08:26.600 --> 00:08:30.500
 latest version of ALS, which is a 1.3

164
00:08:29.500 --> 00:08:32.600
 or better security.

165
00:08:33.300 --> 00:08:37.600
And we will also investigate the

166
00:08:36.600 --> 00:08:40.000
 TLs version 1.3.

167
00:08:40.800 --> 00:08:43.800
And now let's look at the TLs version

168
00:08:43.800 --> 00:08:46.700
 1.3 handshake process.

169
00:08:57.900 --> 00:09:00.800
Now, let's see how the TLs handshake

170
00:09:00.800 --> 00:09:03.500
 process progresses in TLS version

171
00:09:03.500 --> 00:09:07.100
 one 1.3 the latest

172
00:09:06.100 --> 00:09:09.600
 version as you know, so let's

173
00:09:09.600 --> 00:09:12.300
 look at what happens in a PLS

174
00:09:12.300 --> 00:09:15.200
 and shake after TCP connection is established.

175
00:09:16.100 --> 00:09:19.400
TLS handshake starts when the client

176
00:09:19.400 --> 00:09:22.800
 sends a client Hello message to

177
00:09:22.800 --> 00:09:25.100
 the server. So there is a

178
00:09:25.100 --> 00:09:28.900
 client Hello message from the client to the

179
00:09:28.900 --> 00:09:29.900
 server and

180
00:09:31.300 --> 00:09:34.400
there are some extensions in this message.

181
00:09:35.100 --> 00:09:38.700
And let's take a look at what these extensions are

182
00:09:38.700 --> 00:09:41.500
 at the structure of the clientele. Hello

183
00:09:41.500 --> 00:09:44.600
 packet in Wireshark. So we

184
00:09:44.600 --> 00:09:48.600
 will compare this this messaging with

185
00:09:47.600 --> 00:09:51.000
 the Wireshark packets

186
00:09:50.000 --> 00:09:52.200
 details.

187
00:09:57.300 --> 00:10:01.200
So advise shark, we will examine handshake packets

188
00:10:00.200 --> 00:10:04.100
 on decrypted traffic because we

189
00:10:03.100 --> 00:10:06.500
 can't see many details when it

190
00:10:06.500 --> 00:10:09.900
 is encrypted. Also some of the handshake packets

191
00:10:09.900 --> 00:10:10.400
 appear.

192
00:10:11.200 --> 00:10:13.000
AS application data

193
00:10:13.800 --> 00:10:14.000
and

194
00:10:14.900 --> 00:10:18.700
Van encrypted some of the handshake packets

195
00:10:18.700 --> 00:10:21.200
 appear AS application date of any

196
00:10:21.200 --> 00:10:21.700
 group that

197
00:10:22.500 --> 00:10:25.300
you will see how it is decrypted in

198
00:10:25.300 --> 00:10:28.700
 the next lesson. Let's focus now the handshake

199
00:10:28.700 --> 00:10:31.800
 process and the structure of the packets associated

200
00:10:31.800 --> 00:10:34.600
 with the handshake process, and we will

201
00:10:34.600 --> 00:10:38.300
 look at the TLs handshake

202
00:10:37.300 --> 00:10:39.000
 puppets.

203
00:10:39.500 --> 00:10:41.000
first and we can use

204
00:10:41.900 --> 00:10:45.100
the filter expression to investigate

205
00:10:44.100 --> 00:10:47.900
 the packets associated with the TLs

206
00:10:47.900 --> 00:10:51.600
 protocol and you can use this

207
00:10:50.600 --> 00:10:53.300
 filter in here.

208
00:10:56.100 --> 00:10:58.600
Just you can type TLS.

209
00:10:59.000 --> 00:10:59.300
and

210
00:11:00.600 --> 00:11:03.000
click on the enter and as you can see.

211
00:11:04.400 --> 00:11:07.600
Here is a TLS protocol.

212
00:11:08.500 --> 00:11:11.800
And Shake process and it

213
00:11:11.800 --> 00:11:14.300
 begins with the packet if the

214
00:11:14.300 --> 00:11:17.200
 two and we will follow the

215
00:11:17.200 --> 00:11:20.400
 TCP stream in clearly.

216
00:11:21.400 --> 00:11:25.600
a stream in order to see the only the

217
00:11:24.600 --> 00:11:28.400
 handshake traffic people follow

218
00:11:27.400 --> 00:11:30.800
 the TCP string in here and

219
00:11:30.800 --> 00:11:33.900
 our process begins with

220
00:11:33.900 --> 00:11:36.900
 this packet the client hello packet

221
00:11:36.900 --> 00:11:37.600
 so that

222
00:11:38.500 --> 00:11:40.200
we will follow the TCP.

223
00:11:41.600 --> 00:11:44.600
stream in here on this packet and right

224
00:11:44.600 --> 00:11:47.800
 click you can do right click follow

225
00:11:47.800 --> 00:11:51.400
 and TCP stream that we

226
00:11:50.400 --> 00:11:52.300
 will follow

227
00:11:54.600 --> 00:11:58.700
and okay, you can close this window because in

228
00:11:58.700 --> 00:12:02.300
 the background we have the packets now associated

229
00:12:01.300 --> 00:12:02.700
 with the

230
00:12:03.600 --> 00:12:04.400
ALS

231
00:12:05.200 --> 00:12:09.800
and shake and as you can see in here firstly

232
00:12:08.800 --> 00:12:12.100
 we can see the TCP handshake

233
00:12:11.100 --> 00:12:12.900
 packets in.

234
00:12:14.500 --> 00:12:17.100
The beginning with a scene packet the

235
00:12:17.100 --> 00:12:20.500
 connection the communication begins with

236
00:12:20.500 --> 00:12:22.900
 the scene packet then.

237
00:12:25.600 --> 00:12:27.400
Here is a thin egg packet.

238
00:12:28.500 --> 00:12:31.800
As the second packet and at the

239
00:12:31.800 --> 00:12:34.000
 end of the TCP and Shake.

240
00:12:34.600 --> 00:12:38.400
connection ISP handshake communication the egg

241
00:12:37.400 --> 00:12:40.800
 message in here so scene and

242
00:12:40.800 --> 00:12:44.100
 Scenic and egg messages in

243
00:12:43.100 --> 00:12:46.800
 here to establish a

244
00:12:46.800 --> 00:12:49.800
 TCP connection before the TLs and

245
00:12:50.600 --> 00:12:51.800
and we have now.

246
00:12:52.700 --> 00:12:56.600
By the packet 501 we

247
00:12:55.600 --> 00:12:58.400
 have now a TCP connection

248
00:12:58.400 --> 00:13:01.100
 between the client and the server.

249
00:13:01.600 --> 00:13:01.900
so

250
00:13:03.200 --> 00:13:03.500
and

251
00:13:05.200 --> 00:13:09.000
at this point the TLs handshake

252
00:13:08.500 --> 00:13:10.100
 process begins

253
00:13:10.800 --> 00:13:12.600
with the packet 52

254
00:13:13.300 --> 00:13:16.900
and we will investigate on this packet

255
00:13:16.900 --> 00:13:19.500
 decline Hello message the

256
00:13:19.500 --> 00:13:20.600
 client. Hello Tech.

257
00:13:21.200 --> 00:13:24.400
So packet 52 is

258
00:13:24.400 --> 00:13:27.100
 a client. Hello packet as you can see in here.

259
00:13:27.800 --> 00:13:30.700
And we have the packet details as

260
00:13:30.700 --> 00:13:31.100
 well.

261
00:13:32.100 --> 00:13:32.400
So

262
00:13:33.600 --> 00:13:36.800
now we will expand the details in

263
00:13:36.800 --> 00:13:37.200
 here.

264
00:13:38.900 --> 00:13:42.100
The transport layer security field. I

265
00:13:41.100 --> 00:13:45.000
 am expanding it and then we

266
00:13:44.300 --> 00:13:47.800
 can see the TLs version 1.3.

267
00:13:48.800 --> 00:13:50.300
And let's expand it.

268
00:13:51.100 --> 00:13:52.100
so in here

269
00:13:53.100 --> 00:13:56.500
the version of the client hello packet appears to

270
00:13:56.500 --> 00:14:01.400
 be 1.0 1.0 as

271
00:14:00.400 --> 00:14:03.200
 you can see TLS version

272
00:14:03.200 --> 00:14:06.500
 is 1.0 because the

273
00:14:06.500 --> 00:14:09.900
 client sends this message with the lowest TLS

274
00:14:09.900 --> 00:14:13.200
 version it can send the Terrace

275
00:14:12.200 --> 00:14:15.900
 version is one point zero.

276
00:14:16.500 --> 00:14:19.300
And this requirement is specified in the

277
00:14:19.300 --> 00:14:22.900
 RFC document of the TLs protocol and

278
00:14:22.900 --> 00:14:26.000
 it also shows and asks the

279
00:14:25.400 --> 00:14:28.900
 client also shows and ask the

280
00:14:28.900 --> 00:14:31.800
 TLs versions that they

281
00:14:31.800 --> 00:14:34.600
 can't talk to the server in this packet.

282
00:14:34.600 --> 00:14:37.200
 So the client says to the

283
00:14:37.200 --> 00:14:40.400
 server a server. I am supporting these

284
00:14:40.400 --> 00:14:42.100
 versions of the TLs.

285
00:14:42.700 --> 00:14:45.400
And we can see the other.

286
00:14:46.400 --> 00:14:49.600
Versions of the TLs which the

287
00:14:49.600 --> 00:14:52.700
 clients support currently and you

288
00:14:52.700 --> 00:14:55.800
 can find this version

289
00:14:55.800 --> 00:14:58.800
 information in the extensions.

290
00:14:59.700 --> 00:15:02.400
And that extension is

291
00:15:02.400 --> 00:15:06.100
 in here the supported versions

292
00:15:05.100 --> 00:15:09.200
 extension. You can expand this

293
00:15:08.200 --> 00:15:11.300
 extension and you can

294
00:15:11.300 --> 00:15:14.700
 see the supported versions in

295
00:15:14.700 --> 00:15:16.000
 here as you can see.

296
00:15:17.700 --> 00:15:21.200
So as you can see the client supports

297
00:15:20.200 --> 00:15:23.300
 the TLs version

298
00:15:23.300 --> 00:15:26.300
 1.2 at the

299
00:15:26.300 --> 00:15:29.400
 TLs version 1.3. In this

300
00:15:29.400 --> 00:15:33.200
 case, the server will choose the highest the latest

301
00:15:32.200 --> 00:15:34.300
 version it has.

302
00:15:35.100 --> 00:15:39.100
And so it will probably choose TLS version

303
00:15:38.100 --> 00:15:41.100
 1.3.

304
00:15:41.800 --> 00:15:45.100
And when we look at the server hello

305
00:15:44.100 --> 00:15:46.200
 packet.

306
00:15:47.300 --> 00:15:51.900
You will see the TLs version 1.3 that

307
00:15:51.900 --> 00:15:54.000
 the server has chosen.

308
00:15:55.100 --> 00:15:58.200
And let's look at in here you can see.

309
00:15:59.300 --> 00:16:02.300
the supported version in here

310
00:16:03.200 --> 00:16:06.600
And here is you can see in the server Hello

311
00:16:06.600 --> 00:16:09.500
 message packet. The server

312
00:16:09.500 --> 00:16:13.100
 says yes. I am also supporting details version

313
00:16:12.100 --> 00:16:15.700
 1.3 and

314
00:16:15.700 --> 00:16:18.600
 we can talk in this TLS version

315
00:16:18.600 --> 00:16:21.900
 we can talk to each other with this

316
00:16:21.900 --> 00:16:24.400
 TLS version as we get

317
00:16:24.400 --> 00:16:28.000
 before the server would choose

318
00:16:27.200 --> 00:16:31.800
 the TRS version 1.3.

319
00:16:32.600 --> 00:16:35.200
The keep in mind that and turn back

320
00:16:35.200 --> 00:16:39.000
 to the clientele message again and let me

321
00:16:38.500 --> 00:16:41.200
 close this extensions.

322
00:16:43.200 --> 00:16:44.700
this extensions and

323
00:16:47.400 --> 00:16:48.600
we will expand later.

324
00:16:49.700 --> 00:16:50.000
them

325
00:16:53.600 --> 00:16:55.100
Let me close them now.

326
00:17:00.200 --> 00:17:02.000
Not to confuse you.

327
00:17:02.500 --> 00:17:03.900
and in here

328
00:17:04.900 --> 00:17:08.100
the second important point

329
00:17:07.100 --> 00:17:08.800
 is

330
00:17:09.600 --> 00:17:13.800
About the client Hello message

331
00:17:12.800 --> 00:17:15.700
 so we

332
00:17:15.700 --> 00:17:18.300
 can say that when we come

333
00:17:18.300 --> 00:17:21.700
 to the blind. Hello part and Shake protocol.

334
00:17:21.700 --> 00:17:25.600
 We see that the version TLS. Let

335
00:17:24.600 --> 00:17:25.700
 me

336
00:17:26.400 --> 00:17:30.800
Shove you we come to the handshake protocol

337
00:17:30.800 --> 00:17:33.200
 client. Hello part as you

338
00:17:33.200 --> 00:17:36.400
 can see in here, we can see the version is

339
00:17:36.400 --> 00:17:38.100
 TLS 1.2.

340
00:17:39.100 --> 00:17:42.900
Not the 1.0 or 1.3. We

341
00:17:42.900 --> 00:17:43.800
 can see the version is.

342
00:17:45.700 --> 00:17:48.700
The version is 1.2. And the

343
00:17:48.700 --> 00:17:52.000
 client says that with this version. Hey,

344
00:17:51.700 --> 00:17:54.900
 as I as I am also supporting

345
00:17:54.900 --> 00:17:58.200
 supporting the version 1.2. I

346
00:17:57.200 --> 00:18:00.800
 am sending a and hello.

347
00:18:00.800 --> 00:18:03.500
 Hello message with this version as well

348
00:18:03.500 --> 00:18:07.600
 and we can see the PLS

349
00:18:06.600 --> 00:18:09.700
 version 1.2 in

350
00:18:09.700 --> 00:18:13.000
 here because because the

351
00:18:12.500 --> 00:18:16.100
 another version the

352
00:18:15.100 --> 00:18:17.100
 client has

353
00:18:18.400 --> 00:18:21.500
and when we look at the another part in here,

354
00:18:21.500 --> 00:18:24.700
 we can see the random value a

355
00:18:24.700 --> 00:18:27.800
 random value declined as and the

356
00:18:27.800 --> 00:18:31.500
 client is sending a packet

357
00:18:30.500 --> 00:18:33.500
 with this random value. So

358
00:18:34.200 --> 00:18:38.300
this is a very important value to us in transport layer

359
00:18:37.300 --> 00:18:40.800
 Security in TLS both the

360
00:18:40.800 --> 00:18:43.500
 client and the server Generate random values during

361
00:18:43.500 --> 00:18:46.500
 the initial handshake process. And so

362
00:18:46.500 --> 00:18:49.600
 you will see another random value in the response

363
00:18:49.600 --> 00:18:50.900
 of server as well.

364
00:18:52.300 --> 00:18:55.800
Let's look at the server Hello message. You can

365
00:18:55.800 --> 00:18:59.200
 see another random value in the

366
00:18:58.200 --> 00:19:01.500
 on the server side

367
00:19:01.500 --> 00:19:03.800
 as well as you can see in here.

368
00:19:04.400 --> 00:19:08.100
The server also has a random value that

369
00:19:07.100 --> 00:19:08.900
 it generates.

370
00:19:11.400 --> 00:19:14.800
Before and and we

371
00:19:14.800 --> 00:19:17.800
 turn back to the client have a message. The client

372
00:19:17.800 --> 00:19:20.100
 also has a random value.

373
00:19:21.100 --> 00:19:25.300
So these random values are used as input

374
00:19:24.300 --> 00:19:27.700
 to generate the session keys

375
00:19:27.700 --> 00:19:31.100
 that are used to encrypt and decrypt data

376
00:19:30.100 --> 00:19:33.400
 exchanged during this session.

377
00:19:33.400 --> 00:19:36.600
 Specifically the random values are used as

378
00:19:36.600 --> 00:19:40.100
 inputs to a key exchange algorithm

379
00:19:39.100 --> 00:19:42.900
 such as the DP algorithm to

380
00:19:42.900 --> 00:19:45.800
 generate a shared secret that is

381
00:19:45.800 --> 00:19:49.100
 then used to drive the session keys.

382
00:19:48.100 --> 00:19:51.500
 And once the shared

383
00:19:51.500 --> 00:19:54.800
 once the shared secret is generated. It

384
00:19:54.800 --> 00:19:58.100
 is used as an input to a key

385
00:19:57.100 --> 00:20:01.400
 Drive derivation and input to

386
00:20:00.400 --> 00:20:03.800
 a key derivation function. It

387
00:20:03.800 --> 00:20:06.600
 is the shared screen the

388
00:20:06.600 --> 00:20:09.700
 shared secret is used as an input

389
00:20:09.700 --> 00:20:14.300
 to a key Drive derivation function

390
00:20:13.300 --> 00:20:16.100
 and in order to

391
00:20:16.100 --> 00:20:18.800
 generate the session keys.

392
00:20:20.600 --> 00:20:23.400
To sum up once the shared secret is

393
00:20:23.400 --> 00:20:26.600
 generated. It is used as an input

394
00:20:26.600 --> 00:20:30.200
 a key derivation function in

395
00:20:29.200 --> 00:20:32.100
 order to generate the session Keys. Keep

396
00:20:32.100 --> 00:20:32.400
 in mind.

397
00:20:33.400 --> 00:20:36.300
So the session keys are used to encrypt and

398
00:20:36.300 --> 00:20:39.800
 decrypt data exchanged during this session.

399
00:20:39.800 --> 00:20:42.400
 The random values also used to

400
00:20:42.400 --> 00:20:45.800
 ensure that the session keys are unique and not

401
00:20:45.800 --> 00:20:48.800
 predictable which helps to protect

402
00:20:48.800 --> 00:20:52.600
 against certain types of attacks additionally

403
00:20:51.600 --> 00:20:55.300
 the use of random

404
00:20:54.300 --> 00:20:58.200
 values in the key exchange process

405
00:20:57.200 --> 00:21:00.400
 has to ensure that the

406
00:21:00.400 --> 00:21:03.800
 shared secret is also unique and not predictable

407
00:21:03.800 --> 00:21:07.100
 if the shared secret was predictable and

408
00:21:06.100 --> 00:21:09.900
 attacker could potentially intercept it

409
00:21:09.900 --> 00:21:13.400
 and use it to decrypted exchange

410
00:21:12.400 --> 00:21:15.400
 during this session.

411
00:21:16.400 --> 00:21:19.400
So remember that always and to sum up

412
00:21:19.400 --> 00:21:23.300
 the use of random values in the key exchange

413
00:21:22.300 --> 00:21:25.200
 process in tears version

414
00:21:25.200 --> 00:21:28.600
 1.3 helps to ensure

415
00:21:28.600 --> 00:21:31.800
 that the session keys and shared secret

416
00:21:31.800 --> 00:21:35.600
 are unique and not predictable which

417
00:21:34.600 --> 00:21:38.000
 helps to protect against a

418
00:21:37.500 --> 00:21:41.500
 certain types of attacks and ensures forward

419
00:21:40.500 --> 00:21:42.200
 secrecy.

420
00:21:42.900 --> 00:21:44.100
Don't forget that.

421
00:21:44.900 --> 00:21:48.500
So when we look at the cipher streets

422
00:21:48.500 --> 00:21:51.100
 on the other hand, we we will

423
00:21:51.100 --> 00:21:51.400
 also.

424
00:21:52.300 --> 00:21:55.300
See another specific and the

425
00:21:55.300 --> 00:21:59.900
 important information about the cryptographic

426
00:21:58.900 --> 00:22:00.800
 algorithms.

427
00:22:01.400 --> 00:22:05.400
Maybe some of you know these algorithms

428
00:22:04.400 --> 00:22:07.400
 before and we will

429
00:22:07.400 --> 00:22:10.600
 talk about The Cypher streets in here as you

430
00:22:10.600 --> 00:22:11.100
 can see.

431
00:22:12.300 --> 00:22:15.600
In the figure as well. We

432
00:22:15.600 --> 00:22:18.600
 have as a Cypher. So it's

433
00:22:18.600 --> 00:22:22.700
 in the client Hello message and we

434
00:22:21.700 --> 00:22:24.800
 will talk about The Cypher sweets

435
00:22:24.800 --> 00:22:27.600
 now, so in declined Hello message

436
00:22:27.600 --> 00:22:30.900
 and the extension of Cipher streets.

437
00:22:31.500 --> 00:22:33.900
the extension of Cypher sweets

438
00:22:34.700 --> 00:22:38.000
is used to indicate the cryptographic algorithms

439
00:22:37.400 --> 00:22:40.300
 that decline supports for the

440
00:22:40.300 --> 00:22:43.700
 secure connection and perhaps we may

441
00:22:43.700 --> 00:22:46.300
 say it is also used to indicate that

442
00:22:46.300 --> 00:22:49.400
 the client is willing to use for the secure

443
00:22:49.400 --> 00:22:52.400
 communication session. The extension is

444
00:22:52.400 --> 00:22:56.300
 identified by the type supported groups.

445
00:22:57.200 --> 00:22:57.700
Maybe

446
00:22:58.600 --> 00:23:01.100
you will notice that here is a

447
00:23:01.100 --> 00:23:02.600
 support group.

448
00:23:03.400 --> 00:23:07.700
And you can also see the support groups

449
00:23:07.700 --> 00:23:08.600
 in other.

450
00:23:09.500 --> 00:23:09.800
parts

451
00:23:12.600 --> 00:23:14.100
supported versions

452
00:23:15.200 --> 00:23:19.400
as you can see in here supported version

453
00:23:19.400 --> 00:23:23.600
 in here is reserved and

454
00:23:22.600 --> 00:23:25.700
 this version and

455
00:23:25.700 --> 00:23:28.600
 when we look at the Cypress streets

456
00:23:29.300 --> 00:23:32.000
On the other hand we can see it.

457
00:23:33.800 --> 00:23:34.800
to in here

458
00:23:35.900 --> 00:23:39.800
The cipher Street support version

459
00:23:39.800 --> 00:23:43.000
 is in here, too.

460
00:23:43.600 --> 00:23:43.800
so

461
00:23:45.100 --> 00:23:47.100
supported groups information

462
00:23:50.100 --> 00:23:51.000
arms from

463
00:23:52.700 --> 00:23:55.600
the another part in here the other

464
00:23:55.600 --> 00:23:58.900
 extensions and you can find in

465
00:23:58.900 --> 00:24:01.900
 the state. Sorry support

466
00:24:01.900 --> 00:24:03.500
 versions information.

467
00:24:04.700 --> 00:24:06.300
in the support versions

468
00:24:07.200 --> 00:24:11.100
and you can check check it also in this part.

469
00:24:10.100 --> 00:24:14.000
 So let's turn back to the cycle seat

470
00:24:13.100 --> 00:24:14.700
 now and

471
00:24:17.100 --> 00:24:20.600
We said that the extension is

472
00:24:20.600 --> 00:24:24.400
 identified by the type support groups

473
00:24:23.400 --> 00:24:25.500
 and the value.

474
00:24:26.100 --> 00:24:29.900
Is a list of support groups encoded as

475
00:24:29.900 --> 00:24:32.400
 a list of two byte value?

476
00:24:33.400 --> 00:24:34.700
So you can see.

477
00:24:36.200 --> 00:24:39.700
It is a 2 byte values in here

478
00:24:39.700 --> 00:24:40.900
 support groups.

479
00:24:41.600 --> 00:24:43.600
and supported groups in here

480
00:24:46.700 --> 00:24:50.000
and you can see the support group information in

481
00:24:49.600 --> 00:24:52.100
 the extension supported groups.

482
00:24:52.900 --> 00:24:56.100
I have told you wrongly before

483
00:24:55.100 --> 00:24:58.200
 I have said you can

484
00:24:58.200 --> 00:25:01.800
 see the support versions. It is not true. I'm

485
00:25:01.800 --> 00:25:02.100
 sorry.

486
00:25:03.400 --> 00:25:06.500
My apologize to this and you can see

487
00:25:06.500 --> 00:25:09.800
 the support groups in the extension support

488
00:25:09.800 --> 00:25:12.100
 groups. And when we look at the

489
00:25:12.100 --> 00:25:15.300
 support groups data, you can see the

490
00:25:15.300 --> 00:25:18.700
 support group as the reserved one

491
00:25:18.700 --> 00:25:21.700
 in here. And this group is

492
00:25:21.700 --> 00:25:24.300
 also used in the cipher Street

493
00:25:24.300 --> 00:25:28.000
 field Cipher sweets as you can see the

494
00:25:27.200 --> 00:25:29.800
 same supported group in here.

495
00:25:30.600 --> 00:25:30.800
and

496
00:25:32.700 --> 00:25:35.600
it is encoded as a list of 2

497
00:25:35.600 --> 00:25:37.500
 byte values in here.

498
00:25:38.800 --> 00:25:39.800
And you can check.

499
00:25:40.800 --> 00:25:41.400
whether it

500
00:25:43.300 --> 00:25:46.900
has two byte values in the packet

501
00:25:46.900 --> 00:25:47.900
 bytes pain.

502
00:25:49.400 --> 00:25:49.900
I will.

503
00:25:50.700 --> 00:25:53.100
Show you the packet bytes.

504
00:25:53.600 --> 00:25:54.200
in here

505
00:25:56.200 --> 00:25:57.800
and when we

506
00:25:58.400 --> 00:26:00.200
Make closer in here.

507
00:26:01.500 --> 00:26:02.300
You can see now.

508
00:26:03.900 --> 00:26:06.300
Let me resize the window in here.

509
00:26:09.800 --> 00:26:13.200
And you can see the another part. So in

510
00:26:12.200 --> 00:26:15.500
 here the supported group

511
00:26:15.500 --> 00:26:18.300
 encoded as a list of

512
00:26:18.300 --> 00:26:21.700
 two byte values and when we

513
00:26:21.700 --> 00:26:25.100
 click on this information, you can

514
00:26:24.100 --> 00:26:28.100
 see it corresponds to

515
00:26:27.100 --> 00:26:30.400
 the two byte values

516
00:26:30.400 --> 00:26:33.400
 on the packet bytes pane.

517
00:26:33.400 --> 00:26:34.600
 You can see in here.

518
00:26:35.500 --> 00:26:37.300
when we click on this value

519
00:26:38.100 --> 00:26:42.400
It is responding to bytes values

520
00:26:41.400 --> 00:26:43.800
 in the packed bytes.

521
00:26:44.300 --> 00:26:47.800
So click on let's look at it corresponds

522
00:26:47.800 --> 00:26:49.500
 to the two bytes value.

523
00:26:50.100 --> 00:26:53.700
Okay, the cipher switch extension in

524
00:26:53.700 --> 00:26:55.700
 the client Hello message.

525
00:26:56.500 --> 00:26:58.900
Let's turn back to the side for sweets.

526
00:27:00.900 --> 00:27:03.700
Decide for Suite extension in the client Hello

527
00:27:03.700 --> 00:27:06.800
 message includes a list of supported Cipher

528
00:27:06.800 --> 00:27:09.700
 streets in here as you can see and there

529
00:27:09.700 --> 00:27:12.300
 are 16 seats in here

530
00:27:12.300 --> 00:27:12.600
 now.

531
00:27:15.900 --> 00:27:19.000
We have 16 algorithms in

532
00:27:18.500 --> 00:27:21.900
 here and there corresponding

533
00:27:21.900 --> 00:27:25.200
 chords. Also we

534
00:27:24.200 --> 00:27:25.700
 can see.

535
00:27:26.300 --> 00:27:29.700
In here there corresponding because in

536
00:27:29.700 --> 00:27:32.700
 at the end of the algorithm name,

537
00:27:32.700 --> 00:27:35.700
 we can see their corresponding quotes

538
00:27:35.700 --> 00:27:38.300
 which This Server can use to

539
00:27:38.300 --> 00:27:41.500
 choose the suitable Cipher suite for the session.

540
00:27:41.500 --> 00:27:44.700
 So declined will typically include

541
00:27:44.700 --> 00:27:47.200
 a list of Cypress seeds in order

542
00:27:47.200 --> 00:27:51.000
 of preference as I told you the client

543
00:27:50.100 --> 00:27:53.100
 will typically include a list

544
00:27:53.100 --> 00:27:57.200
 of Cypher. So it's in order of preference with

545
00:27:56.200 --> 00:27:59.700
 most preferred Cipher Street

546
00:27:59.700 --> 00:28:02.700
 listed first and in here the

547
00:28:02.700 --> 00:28:08.400
 TLs AES 128 GCM

548
00:28:06.400 --> 00:28:09.700
 s h

549
00:28:09.700 --> 00:28:12.700
 a 256 is

550
00:28:12.700 --> 00:28:15.400
 the most preferred one

551
00:28:15.400 --> 00:28:17.600
 as a Cypress Street.

552
00:28:18.300 --> 00:28:21.900
So server will choose this one.

553
00:28:22.700 --> 00:28:23.700
most likely

554
00:28:24.700 --> 00:28:27.400
then look at the server side

555
00:28:27.400 --> 00:28:31.300
 servers Hello message. We will see this Cipher

556
00:28:30.300 --> 00:28:33.500
 Street has been chosen by

557
00:28:33.500 --> 00:28:34.400
 the server.

558
00:28:35.200 --> 00:28:38.500
And when we look at the chosen Cipher Suite

559
00:28:38.500 --> 00:28:42.800
 on the server Hello message, we will see this Cipher

560
00:28:41.800 --> 00:28:44.300
 Suite in here. Let's look at

561
00:28:44.300 --> 00:28:44.500
 this.

562
00:28:45.400 --> 00:28:49.300
As you can see the cipher Suite has

563
00:28:48.300 --> 00:28:52.000
 been chosen as TLS.

564
00:28:52.600 --> 00:28:56.000
AES 128 GCM

565
00:28:55.100 --> 00:29:00.100
 sha 256 or

566
00:28:59.100 --> 00:29:02.500
 you can see the corresponding quotes

567
00:29:02.500 --> 00:29:06.600
 in here 1000 300

568
00:29:05.600 --> 00:29:08.900
 and one and

569
00:29:08.900 --> 00:29:11.800
 when we look at clientele message, we

570
00:29:11.800 --> 00:29:14.800
 will see the disciple treat at first

571
00:29:14.800 --> 00:29:17.000
 in the Cypress streets part.

572
00:29:17.600 --> 00:29:19.200
Let's look at the clientele.

573
00:29:20.200 --> 00:29:22.800
As you can see it is the same one.

574
00:29:23.900 --> 00:29:26.900
The same Cipher suite at the

575
00:29:26.900 --> 00:29:30.600
 first line in here, so and

576
00:29:29.600 --> 00:29:32.500
 we can understand that it

577
00:29:32.500 --> 00:29:35.600
 is listed in order of preference since

578
00:29:35.600 --> 00:29:38.100
 the cryptographic algorithm that the server

579
00:29:38.100 --> 00:29:41.000
 choose in its response message is

580
00:29:41.300 --> 00:29:45.100
 the first algorithm here when we look at the server side,

581
00:29:45.100 --> 00:29:48.400
 we could have seen the sign for

582
00:29:48.400 --> 00:29:51.600
 sheet and the server choose this algorithm in

583
00:29:51.600 --> 00:29:54.600
 its answer the children. Algorithm

584
00:29:54.600 --> 00:29:57.200
 is the first one offered in the client message.

585
00:29:58.300 --> 00:29:59.800
We have noticed that.

586
00:30:13.900 --> 00:30:16.500
Okay, let's move on to investigate the

587
00:30:16.500 --> 00:30:19.700
 our packet or client hello

588
00:30:19.700 --> 00:30:22.600
 packet and now we will

589
00:30:22.600 --> 00:30:26.200
 look at the status request extension.

590
00:30:25.200 --> 00:30:27.900
 We will investigate the

591
00:30:28.900 --> 00:30:31.500
status request extension in

592
00:30:31.500 --> 00:30:35.500
 here and you can see the status request

593
00:30:35.500 --> 00:30:36.800
 in here as you

594
00:30:38.900 --> 00:30:42.000
notice in here that and this

595
00:30:41.700 --> 00:30:44.900
 request is used to provide additional

596
00:30:44.900 --> 00:30:47.500
 security by allowing the

597
00:30:47.500 --> 00:30:50.400
 client to verify the status of a server certificate

598
00:30:50.400 --> 00:30:53.200
 before establishing a secure session with

599
00:30:53.200 --> 00:30:53.800
 the server.

600
00:30:54.600 --> 00:30:58.900
And the status request extension includes

601
00:30:57.900 --> 00:31:01.400
 a certificate status

602
00:31:00.400 --> 00:31:02.700
 type value.

603
00:31:03.900 --> 00:31:05.200
As you can see in here.

604
00:31:06.100 --> 00:31:10.400
So it includes a certificate status type field and

605
00:31:09.400 --> 00:31:12.300
 which is used to

606
00:31:12.300 --> 00:31:15.200
 indicate the type of short with status

607
00:31:15.200 --> 00:31:17.400
 that the client is requesting.

608
00:31:18.200 --> 00:31:23.200
One of the types that can be used is ocsp

609
00:31:21.200 --> 00:31:24.100
 which means

610
00:31:24.100 --> 00:31:27.000
 online certificate status protocol.

611
00:31:28.300 --> 00:31:31.600
And which is a protocol that allows the

612
00:31:31.600 --> 00:31:35.400
 client to check the status of a certificate by acquiring and

613
00:31:34.400 --> 00:31:38.300
 by creating an ocsp

614
00:31:37.300 --> 00:31:40.000
 responders server.

615
00:31:40.600 --> 00:31:43.500
Maybe some of you you have heard

616
00:31:43.500 --> 00:31:46.400
 it before and when the clients

617
00:31:46.400 --> 00:31:49.800
 sends the client hello packet with the

618
00:31:49.800 --> 00:31:51.300
 status request extension.

619
00:31:52.500 --> 00:31:55.900
It includes the certificate States

620
00:31:55.900 --> 00:31:59.100
 type value in here with this

621
00:31:58.100 --> 00:32:01.300
 data to indicate that it would

622
00:32:01.300 --> 00:32:04.800
 like to check the status of the server certificate

623
00:32:04.800 --> 00:32:07.500
 using the ocsp protocol.

624
00:32:08.800 --> 00:32:12.300
In here the ocsp protocol

625
00:32:11.300 --> 00:32:14.900
 the server if it supports

626
00:32:14.900 --> 00:32:17.600
 this type of extension will include the

627
00:32:17.600 --> 00:32:20.500
 status request will include the status request

628
00:32:20.500 --> 00:32:23.700
 extension in the server help packet and we

629
00:32:23.700 --> 00:32:26.700
 will see this extension later on the

630
00:32:26.700 --> 00:32:29.500
 response packet and the necessary

631
00:32:29.500 --> 00:32:32.400
 information to check the status of

632
00:32:32.400 --> 00:32:35.800
 the shortcut like the ocsp responder

633
00:32:35.800 --> 00:32:39.900
 URL and the ocsp responder ID

634
00:32:38.900 --> 00:32:41.200
 parameters. We will see

635
00:32:41.200 --> 00:32:44.900
 in the server response packet.

636
00:32:45.800 --> 00:32:49.500
With this information when the

637
00:32:49.500 --> 00:32:52.100
 client receives the response packet from the

638
00:32:52.100 --> 00:32:55.600
 server it can use the information provided the

639
00:32:55.600 --> 00:32:58.400
 status request extension to

640
00:32:58.400 --> 00:33:01.900
 check the status of the server recertificate. This

641
00:33:01.900 --> 00:33:04.500
 allows the client to verify that the service sort

642
00:33:04.500 --> 00:33:07.100
 of code is seta valid and hasn't been

643
00:33:07.100 --> 00:33:10.900
 revoked before establishing a secure

644
00:33:10.900 --> 00:33:12.000
 session with the server.

645
00:33:12.600 --> 00:33:15.800
And so this extension is

646
00:33:15.800 --> 00:33:16.400
 used to

647
00:33:17.700 --> 00:33:20.000
check the certificate.

648
00:33:21.000 --> 00:33:21.700
validation

649
00:33:22.800 --> 00:33:24.200
as I told you before

650
00:33:25.200 --> 00:33:26.400
and when we look at the

651
00:33:31.900 --> 00:33:34.600
Client Hello message. We will move

652
00:33:34.600 --> 00:33:38.100
 on the clientele message and I'm closing

653
00:33:37.100 --> 00:33:40.100
 the status request extension now.

654
00:33:40.700 --> 00:33:45.500
Now, let's look at the extension PS

655
00:33:44.500 --> 00:33:45.700
 key.

656
00:33:47.100 --> 00:33:50.300
Or we can say pure shared

657
00:33:50.300 --> 00:33:52.400
 key exchange modes.

658
00:33:53.300 --> 00:33:56.300
Let's expand this extension now and

659
00:33:56.300 --> 00:34:00.200
 we will talk about it a PSG or

660
00:33:59.200 --> 00:34:02.500
 a period a shared key

661
00:34:02.500 --> 00:34:06.300
 is a shared secret that a

662
00:34:05.300 --> 00:34:08.300
 PS key is a shared secret that is

663
00:34:08.300 --> 00:34:11.700
 established and exchanged between the

664
00:34:11.700 --> 00:34:14.400
 client and the server prior to

665
00:34:14.400 --> 00:34:17.600
 the start of the TLs session. The extension

666
00:34:17.600 --> 00:34:20.800
 is used to negotiate the use of PS keys

667
00:34:20.800 --> 00:34:23.400
 with the server which allows both the

668
00:34:23.400 --> 00:34:26.400
 client and server to establish station keys that are

669
00:34:26.400 --> 00:34:30.100
 derived from the pure shared secret

670
00:34:29.100 --> 00:34:33.000
 and ensuring ensuring

671
00:34:32.400 --> 00:34:34.200
 security of the session.

672
00:34:35.300 --> 00:34:38.900
So to do this we have the PSG

673
00:34:38.900 --> 00:34:41.500
 exchange mode information in the

674
00:34:41.500 --> 00:34:42.800
 client Hello message.

675
00:34:43.600 --> 00:34:46.200
and when we look at the another extension

676
00:34:46.900 --> 00:34:50.100
the application layer protocol negotiation

677
00:34:51.600 --> 00:34:55.900
we can see the a LPN information

678
00:34:55.900 --> 00:34:58.800
 in here and Alp and

679
00:34:58.800 --> 00:35:01.800
 protocol which means application layer

680
00:35:01.800 --> 00:35:03.600
 protocol negotiation.

681
00:35:04.600 --> 00:35:07.100
Alpian allows the

682
00:35:07.100 --> 00:35:10.600
 client and the server to negotiate which application layers

683
00:35:10.600 --> 00:35:13.900
 protocol to sorry the

684
00:35:13.900 --> 00:35:16.600
 Alp and allows declined and

685
00:35:16.600 --> 00:35:19.700
 the server to negotiate which application layer protocol to

686
00:35:19.700 --> 00:35:23.900
 use for the session such as HTTP version

687
00:35:23.900 --> 00:35:28.600
 2 or HTTP version 1.1

688
00:35:27.600 --> 00:35:30.200
 without the need for

689
00:35:30.200 --> 00:35:32.600
 a separate negotiation process.

690
00:35:33.400 --> 00:35:36.400
So this can help to improve the performance and

691
00:35:36.400 --> 00:35:39.400
 the security of the session by allowing the

692
00:35:39.400 --> 00:35:43.500
 client and the server to use the most suitable

693
00:35:42.500 --> 00:35:45.300
 protocol for their needs.

694
00:35:47.200 --> 00:35:51.000
and the server can select the most suitable protocol

695
00:35:50.900 --> 00:35:54.100
 based on its available resources

696
00:35:53.100 --> 00:35:56.700
 and the features provided by the

697
00:35:56.700 --> 00:36:00.100
 protocol and here is the client

698
00:35:59.100 --> 00:36:04.400
 represents some HTTP

699
00:36:02.400 --> 00:36:06.000
 protocol in

700
00:36:05.300 --> 00:36:07.200
 here and

701
00:36:08.200 --> 00:36:12.100
when we look at the related server response

702
00:36:11.100 --> 00:36:12.200
 here.

703
00:36:14.300 --> 00:36:15.600
in here you can see

704
00:36:16.400 --> 00:36:20.500
And they're related packet is the packet 61

705
00:36:19.500 --> 00:36:22.400
 that we can see the

706
00:36:22.400 --> 00:36:26.300
 chosen alpn value.

707
00:36:28.200 --> 00:36:31.700
And we will look at the alpn value in

708
00:36:31.700 --> 00:36:31.800
 here.

709
00:36:32.600 --> 00:36:36.300
So you can see the same extension in the server

710
00:36:35.300 --> 00:36:38.500
 response and other server response

711
00:36:38.500 --> 00:36:41.800
 packet not the server hello packet and

712
00:36:41.800 --> 00:36:45.800
 you can see the Alpine value

713
00:36:44.800 --> 00:36:47.400
 in here. We see that

714
00:36:47.400 --> 00:36:51.400
 the alpian preference is H2,

715
00:36:50.400 --> 00:36:54.000
 which means HTTP version

716
00:36:53.000 --> 00:36:54.300
 2.

717
00:36:55.200 --> 00:36:58.700
So that is HTTP version.

718
00:36:58.700 --> 00:37:01.600
 That is HTTP version 2.

719
00:37:05.300 --> 00:37:08.600
And let's turn back to the client Hello message again.

720
00:37:10.200 --> 00:37:14.800
And we can close now the alpian fields.

721
00:37:15.500 --> 00:37:17.100
Don't forget the clients.

722
00:37:17.800 --> 00:37:20.900
Over an LPN protocol type

723
00:37:20.900 --> 00:37:24.200
 as http/2 and

724
00:37:23.200 --> 00:37:26.600
 the server says that hey, okay,

725
00:37:26.600 --> 00:37:30.200
 we can talk to each other using HTTP

726
00:37:29.200 --> 00:37:33.000
 to so it means that HTTP 2

727
00:37:32.400 --> 00:37:35.400
 is okay for me as well

728
00:37:35.400 --> 00:37:38.400
 and they will talk to each other

729
00:37:38.400 --> 00:37:42.100
 using the HTTP version 2

730
00:37:41.100 --> 00:37:44.400
 protocol later as you

731
00:37:44.400 --> 00:37:46.300
 can see in the traffic.

732
00:37:47.100 --> 00:37:49.400
the http/2 packets

733
00:37:50.500 --> 00:37:54.900
So, okay now we can close the alpn application

734
00:37:53.900 --> 00:37:57.400
 layer protocol negotiation extension

735
00:37:56.400 --> 00:37:59.000
 and we can close the

736
00:37:59.600 --> 00:38:00.900
 status request and the other ones.

737
00:38:02.100 --> 00:38:04.000
We should close them.

738
00:38:05.500 --> 00:38:06.900
not confuse

739
00:38:08.600 --> 00:38:09.000
each other

740
00:38:10.300 --> 00:38:10.600
and

741
00:38:12.800 --> 00:38:14.300
let me close these ones.

742
00:38:16.800 --> 00:38:17.200
Okay.

743
00:38:18.600 --> 00:38:21.600
Okay. Now we will investigate the

744
00:38:21.600 --> 00:38:24.200
 key share, okay.

745
00:38:25.100 --> 00:38:29.300
One of the most important extension is Keyshia.

746
00:38:30.200 --> 00:38:32.400
and you can see also in the

747
00:38:33.400 --> 00:38:37.100
illustration of the TLs and

748
00:38:36.100 --> 00:38:37.600
 Shake

749
00:38:38.800 --> 00:38:42.800
We have a g Share value extension.

750
00:38:43.600 --> 00:38:47.400
Within the clientele message and decline

751
00:38:46.400 --> 00:38:50.100
 is sanding a key

752
00:38:49.100 --> 00:38:52.800
 share to the server in the

753
00:38:52.800 --> 00:38:55.400
 client. Hello Tech. So let's

754
00:38:55.400 --> 00:38:56.800
 look at the details now.

755
00:38:59.100 --> 00:39:00.000
We will.

756
00:39:00.900 --> 00:39:03.200
Look at the client. Hello messaging here.

757
00:39:04.400 --> 00:39:07.400
And I will close this one, okay.

758
00:39:09.700 --> 00:39:12.900
Now we should talk about this point

759
00:39:12.900 --> 00:39:15.600
 when a client connects to a

760
00:39:15.600 --> 00:39:18.900
 server the server will present its digital

761
00:39:18.900 --> 00:39:20.200
 certificate.

762
00:39:21.300 --> 00:39:24.900
To the client the shortcut includes information such

763
00:39:24.900 --> 00:39:27.600
 as the servers public key the side the

764
00:39:27.600 --> 00:39:31.500
 service domain name and the digital signature

765
00:39:30.500 --> 00:39:34.300
 of the certificate orderity

766
00:39:33.300 --> 00:39:36.400
 CA you should know

767
00:39:36.400 --> 00:39:40.200
 that issue the shortcut the client

768
00:39:40.200 --> 00:39:43.200
 uses the public key included in the sort of cut to

769
00:39:43.200 --> 00:39:47.200
 encrypt the random value to encrypt its random

770
00:39:46.200 --> 00:39:49.300
 value. It's own random value

771
00:39:49.300 --> 00:39:51.500
 as we can see in the random field.

772
00:39:52.600 --> 00:39:56.100
In here, you can see the clients

773
00:39:55.100 --> 00:39:57.500
 random value.

774
00:39:59.600 --> 00:40:00.400
in here

775
00:40:01.800 --> 00:40:04.400
you can see the random value and

776
00:40:05.500 --> 00:40:08.500
don't forget this the client uses

777
00:40:08.500 --> 00:40:12.000
 the public key to encrypt the random

778
00:40:11.400 --> 00:40:14.500
 value as we can see in the

779
00:40:14.500 --> 00:40:18.000
 random field and since it

780
00:40:17.400 --> 00:40:19.500
 back to the server.

781
00:40:20.800 --> 00:40:23.500
Which then the server uses its

782
00:40:23.500 --> 00:40:26.600
 own private key to decrypt the

783
00:40:26.600 --> 00:40:29.200
 value the decryption of the value by the

784
00:40:29.200 --> 00:40:32.300
 server with its private key proves that

785
00:40:32.300 --> 00:40:35.400
 the server is in position of the

786
00:40:35.400 --> 00:40:36.300
 private key.

787
00:40:37.400 --> 00:40:40.200
So and that the certificate presented by the

788
00:40:40.200 --> 00:40:44.000
 server is true and not tempered

789
00:40:43.000 --> 00:40:44.000
 with.

790
00:40:44.900 --> 00:40:47.800
And this process is called the server key

791
00:40:47.800 --> 00:40:50.600
 exchange and is a

792
00:40:50.600 --> 00:40:54.100
 very of authenticating the servers

793
00:40:53.100 --> 00:40:56.200
 identity to ensure that

794
00:40:56.200 --> 00:40:59.300
 the certificate presented by the server is valid

795
00:40:59.300 --> 00:41:03.200
 the client checks the digital signature

796
00:41:02.200 --> 00:41:05.800
 of the ca shortcut Authority

797
00:41:05.800 --> 00:41:08.600
 that it should sort of good. It

798
00:41:08.600 --> 00:41:12.300
 does saw by using the ca's public

799
00:41:12.300 --> 00:41:15.900
 key, which is typically stored in a local trust

800
00:41:15.900 --> 00:41:18.800
 store. If the signature is valid the

801
00:41:18.800 --> 00:41:21.400
 client can trust that the sword

802
00:41:21.400 --> 00:41:24.500
 was issued by a trust CA and that

803
00:41:24.500 --> 00:41:28.400
 the servers identity has been verified as

804
00:41:27.400 --> 00:41:30.700
 a result. The client uses

805
00:41:30.700 --> 00:41:34.000
 the certificate to verify the servers

806
00:41:33.000 --> 00:41:34.700
 identity.

807
00:41:36.200 --> 00:41:39.300
And we will see that the server

808
00:41:39.300 --> 00:41:42.100
 will share its sort of

809
00:41:42.100 --> 00:41:44.600
 got by this packet.

810
00:41:46.400 --> 00:41:47.200
has been sent

811
00:41:48.400 --> 00:41:51.400
from the server to the client and as a

812
00:41:51.400 --> 00:41:54.300
 result, the client uses the certificate to

813
00:41:54.300 --> 00:41:57.400
 verify the server's identity and to ensure that

814
00:41:57.400 --> 00:42:01.600
 the server is the intended recipient

815
00:42:00.600 --> 00:42:02.700
 of the communication.

816
00:42:03.600 --> 00:42:07.000
So the key share extension when

817
00:42:06.600 --> 00:42:09.700
 we turn back to the teacher extension

818
00:42:09.700 --> 00:42:10.100
 in here.

819
00:42:13.800 --> 00:42:16.400
Let's expand all of the other.

820
00:42:18.800 --> 00:42:22.000
values you can see in here a key

821
00:42:21.500 --> 00:42:23.300
 exchange value

822
00:42:25.300 --> 00:42:28.500
and the key share extension in the client. Hello

823
00:42:28.500 --> 00:42:32.500
 packet is used to convey the key exchange

824
00:42:31.500 --> 00:42:35.200
 parameters for the with this

825
00:42:34.200 --> 00:42:37.800
 key exchange value and for

826
00:42:37.800 --> 00:42:40.900
 the agreed upon key exchange algorithm.

827
00:42:41.900 --> 00:42:42.200
so

828
00:42:43.400 --> 00:42:46.200
And the cheese share extension in the

829
00:42:46.200 --> 00:42:49.300
 client. Hello packet is used to indicate the key

830
00:42:49.300 --> 00:42:52.500
 exchange method that the client supports and

831
00:42:52.500 --> 00:42:56.000
 is willing to use for the session and it also

832
00:42:55.800 --> 00:42:59.400
 includes in this value key

833
00:42:58.400 --> 00:43:02.600
 exchange value also includes the

834
00:43:01.600 --> 00:43:04.100
 clients public key, which is

835
00:43:04.100 --> 00:43:08.500
 used as part of the key exchange process and declines

836
00:43:07.500 --> 00:43:11.100
 publicity is usually usually

837
00:43:10.100 --> 00:43:13.100
 the right from a private key

838
00:43:13.100 --> 00:43:17.500
 that the client generates for the session the public

839
00:43:16.500 --> 00:43:19.400
 key is sent to the

840
00:43:19.400 --> 00:43:22.700
 server with this key

841
00:43:22.700 --> 00:43:23.900
 exchange process.

842
00:43:25.100 --> 00:43:28.300
And the server uses it as part of

843
00:43:28.300 --> 00:43:31.900
 the key exchange process to establish a shared

844
00:43:31.900 --> 00:43:32.100
 Secret.

845
00:43:35.300 --> 00:43:39.100
And just like the client has made

846
00:43:38.100 --> 00:43:41.600
 which will be used to generate

847
00:43:41.600 --> 00:43:44.200
 the session keys. So

848
00:43:46.600 --> 00:43:50.500
after the client sends the necessary parameters

849
00:43:49.500 --> 00:43:53.000
 with the key exchange

850
00:43:52.000 --> 00:43:53.300
 value.

851
00:43:55.100 --> 00:43:59.100
And the necessary options for encryption such

852
00:43:58.100 --> 00:44:03.400
 as cypresseed algorithms

853
00:44:01.400 --> 00:44:04.700
 to the server. The

854
00:44:04.700 --> 00:44:07.700
 server returns a response informing the

855
00:44:07.700 --> 00:44:09.800
 choices it has made.

856
00:44:10.800 --> 00:44:14.400
With the server Hello message and

857
00:44:13.400 --> 00:44:18.200
 the other extensions packet

858
00:44:16.200 --> 00:44:18.800
 later.

859
00:44:20.100 --> 00:44:20.800
and

860
00:44:22.500 --> 00:44:26.000
this becomes the server

861
00:44:25.300 --> 00:44:29.400
 have a packet we can say that this the

862
00:44:28.400 --> 00:44:32.100
 server also generates a random

863
00:44:31.100 --> 00:44:35.100
 value in his sorry in

864
00:44:34.100 --> 00:44:36.700
 its server Hello message.

865
00:44:37.300 --> 00:44:41.100
As you can see Server also has

866
00:44:40.100 --> 00:44:43.400
 a another random value.

867
00:44:45.700 --> 00:44:49.500
that it generates generates and

868
00:44:51.300 --> 00:44:55.200
it's important to note that the key share extension

869
00:44:54.200 --> 00:44:57.900
 is included in both

870
00:44:57.900 --> 00:45:01.600
 the client. Hello and server. Hello

871
00:45:01.600 --> 00:45:02.100
 packets.

872
00:45:02.800 --> 00:45:06.200
As you can see the key share extension

873
00:45:05.200 --> 00:45:09.100
 is in a server Hello

874
00:45:08.100 --> 00:45:09.900
 message as well.

875
00:45:10.700 --> 00:45:15.300
And the server is sanding

876
00:45:13.300 --> 00:45:17.100
 the key exchange

877
00:45:16.100 --> 00:45:19.300
 values too to the

878
00:45:19.300 --> 00:45:22.500
 client side with the server Hello message

879
00:45:22.500 --> 00:45:24.500
 and the clients.

880
00:45:25.500 --> 00:45:28.500
And the clients public

881
00:45:28.500 --> 00:45:31.200
 key is included in the clientele packet and

882
00:45:31.200 --> 00:45:34.700
 the service public key is included in the server.

883
00:45:34.700 --> 00:45:35.700
 Hello packet.

884
00:45:37.800 --> 00:45:41.500
These public keys are used to these

885
00:45:40.500 --> 00:45:43.400
 public keys are used to establish

886
00:45:43.400 --> 00:45:46.600
 the shared secret which will

887
00:45:46.600 --> 00:45:48.700
 be used to generate the session keys.

888
00:45:49.900 --> 00:45:52.600
Keep in mind that everything after

889
00:45:52.600 --> 00:45:56.200
 this phase of the client. Hello

890
00:45:55.200 --> 00:45:59.200
 and the server. Hello packets everything

891
00:45:58.200 --> 00:46:01.800
 after this phase will be

892
00:46:01.800 --> 00:46:03.200
 encrypted.

893
00:46:04.300 --> 00:46:07.900
So since everything will be encrypted

894
00:46:07.900 --> 00:46:11.600
 after the key exchange stage unless

895
00:46:10.600 --> 00:46:12.800
 you decrypt the traffic.

896
00:46:13.500 --> 00:46:16.900
You will see both packets after the

897
00:46:16.900 --> 00:46:20.500
 handshake and the rest as application data.

898
00:46:21.600 --> 00:46:21.900
You will see.

899
00:46:22.800 --> 00:46:25.300
The packets after the

900
00:46:25.300 --> 00:46:28.800
 handshake and the rest of the traffic as

901
00:46:28.800 --> 00:46:31.000
 the application data.

902
00:46:31.900 --> 00:46:36.000
So we can see the decrypted versions

903
00:46:35.200 --> 00:46:39.100
 of the packets in here. So we we

904
00:46:38.100 --> 00:46:41.600
 can see the another.

905
00:46:43.200 --> 00:46:47.600
handshake packets as encrypted extensions, which

906
00:46:46.600 --> 00:46:50.300
 it can whether it

907
00:46:50.300 --> 00:46:54.000
 contains encrypted extensions compressed

908
00:46:53.400 --> 00:46:56.500
 certificate or shortcut verify and

909
00:46:56.500 --> 00:46:59.300
 the other package details we

910
00:46:59.300 --> 00:47:04.400
 can see but without decrypting the

911
00:47:04.400 --> 00:47:04.700
 traffic

912
00:47:05.700 --> 00:47:09.000
So just like in here you can't

913
00:47:08.200 --> 00:47:13.000
 see these packets in clearly. So

914
00:47:11.200 --> 00:47:14.500
 when we

915
00:47:14.500 --> 00:47:18.400
 look at the the version of

916
00:47:19.300 --> 00:47:22.900
Traffic without decrypting. You

917
00:47:22.900 --> 00:47:25.600
 can't see this packets like this.

918
00:47:25.600 --> 00:47:29.200
 You will see the packets AS application

919
00:47:28.200 --> 00:47:32.400
 data in encrypted

920
00:47:31.400 --> 00:47:32.600
 mode.

921
00:47:33.500 --> 00:47:37.500
Let me show you the encrypted

922
00:47:36.500 --> 00:47:40.100
 version of the traffic to

923
00:47:39.100 --> 00:47:40.400
 you.

924
00:47:41.300 --> 00:47:41.700
and

925
00:47:43.100 --> 00:47:43.700
let me

926
00:47:45.500 --> 00:47:48.900
use the same filter again.

927
00:47:49.600 --> 00:47:52.600
And now we are looking the same traffic in

928
00:47:52.600 --> 00:47:52.900
 here.

929
00:47:54.200 --> 00:47:57.800
This is the same traffic. But as you can see after the

930
00:47:57.800 --> 00:48:00.600
 clientele and server. Hello

931
00:48:00.600 --> 00:48:05.000
 messages, you can see the another handshake

932
00:48:03.600 --> 00:48:07.000
 packets AS application

933
00:48:06.000 --> 00:48:07.600
 data.

934
00:48:08.400 --> 00:48:12.500
The packet with number 61

935
00:48:11.500 --> 00:48:15.000
 is an application data

936
00:48:14.400 --> 00:48:17.400
 packet. So there is no details about

937
00:48:17.400 --> 00:48:19.800
 the handshake process.

938
00:48:20.400 --> 00:48:25.100
And you can see the details this TLS

939
00:48:24.100 --> 00:48:27.300
 packets. You can only see

940
00:48:27.300 --> 00:48:31.000
 the application data and it is encrypted mode.

941
00:48:31.600 --> 00:48:34.200
It is in encrypted mode as

942
00:48:34.200 --> 00:48:38.200
 you can see in here. There is a there is an encrypted application

943
00:48:37.200 --> 00:48:38.800
 data.

944
00:48:39.500 --> 00:48:39.900
normal

945
00:48:40.800 --> 00:48:41.900
There is no more information.

946
00:48:44.600 --> 00:48:47.300
In here, but but you can but

947
00:48:47.300 --> 00:48:50.600
 you when you when you

948
00:48:50.600 --> 00:48:53.700
 decrypt when you decrypted traffic, you

949
00:48:53.700 --> 00:48:56.900
 can see the details of

950
00:48:56.900 --> 00:49:00.800
 the TLs packets in

951
00:48:59.800 --> 00:49:04.100
 clearly on Russia.

952
00:49:04.900 --> 00:49:08.600
Let's look at the same packet with the

953
00:49:08.600 --> 00:49:10.000
 decryption.

954
00:49:11.500 --> 00:49:14.600
or with the description process

955
00:49:15.900 --> 00:49:17.900
when we compare

956
00:49:19.100 --> 00:49:22.500
This situation in here.

957
00:49:22.500 --> 00:49:23.600
 Sorry.

958
00:49:24.900 --> 00:49:26.200
So let's look at this.

959
00:49:27.200 --> 00:49:31.800
the same in the same traffic the packet

960
00:49:31.800 --> 00:49:33.400
 61

961
00:49:34.700 --> 00:49:35.000
is

962
00:49:37.200 --> 00:49:39.200
an application data packet

963
00:49:40.100 --> 00:49:41.500
we can see anymore.

964
00:49:43.700 --> 00:49:47.500
the details of the TLs packets

965
00:49:48.400 --> 00:49:52.000
there is no details about the handshake extensions or

966
00:49:51.400 --> 00:49:54.300
 anything any other thing,

967
00:49:54.300 --> 00:49:59.400
 but when we look at the other side

968
00:49:58.400 --> 00:50:03.000
 the decrypted traffic

969
00:50:01.900 --> 00:50:04.800
 we can see

970
00:50:04.800 --> 00:50:05.000
 the

971
00:50:06.700 --> 00:50:08.700
details of the packets in here

972
00:50:10.200 --> 00:50:11.300
You can compare.

973
00:50:12.300 --> 00:50:14.300
These ones easily.

974
00:50:15.100 --> 00:50:19.100
So we can see the details informations. The

975
00:50:18.100 --> 00:50:22.300
 in the detailed information is Packet

976
00:50:21.300 --> 00:50:24.900
 contains encrypted instant

977
00:50:24.900 --> 00:50:27.300
 extensions compressed sort

978
00:50:27.300 --> 00:50:30.800
 kit certificate and the certificate verify

979
00:50:30.800 --> 00:50:33.900
 and the finished message in its own.

980
00:50:33.900 --> 00:50:34.500
 So

981
00:50:36.600 --> 00:50:40.900
but when we look at the packet without

982
00:50:39.900 --> 00:50:43.000
 decryption, we

983
00:50:42.400 --> 00:50:45.500
 just see the application data

984
00:50:45.500 --> 00:50:48.100
 in the pack. There is no detail.

985
00:50:49.900 --> 00:50:50.900
on the other hand

986
00:50:51.900 --> 00:50:53.000
with this packet

987
00:50:57.900 --> 00:51:00.900
We can see all details of the

988
00:51:00.900 --> 00:51:03.800
 TLs handshake packet.

989
00:51:03.800 --> 00:51:06.500
 We can see the all extensions.

990
00:51:07.500 --> 00:51:09.700
all encrypted extensions

991
00:51:10.600 --> 00:51:11.800
under the

992
00:51:12.800 --> 00:51:16.100
handshake protocol encrypted extensions and

993
00:51:15.100 --> 00:51:18.500
 we can also see the certificate in

994
00:51:18.500 --> 00:51:18.600
 here.

995
00:51:19.400 --> 00:51:22.300
You can see here. We can

996
00:51:22.300 --> 00:51:26.500
 see the compressed shortcut values and

997
00:51:25.500 --> 00:51:28.400
 the certificate values.

998
00:51:29.400 --> 00:51:31.100
We can see in here.

999
00:51:32.300 --> 00:51:36.500
But there is no information in the encrypted.

1000
00:51:37.500 --> 00:51:38.000
mode

1001
00:51:39.000 --> 00:51:39.200
so

1002
00:51:41.400 --> 00:51:44.700
to sum up there for we can't clearly

1003
00:51:44.700 --> 00:51:47.200
 see the data for the rest of

1004
00:51:47.200 --> 00:51:49.600
 the handshake without decrypting the traffic.

1005
00:51:50.900 --> 00:51:54.000
And as you can see the following data.

1006
00:51:55.700 --> 00:51:59.200
Is in the form of encrypted application data,

1007
00:51:58.200 --> 00:52:01.200
 however, when the traffic

1008
00:52:01.200 --> 00:52:04.600
 is decrypted we can clearly see the sort of

1009
00:52:04.600 --> 00:52:07.500
 data sent by the server

1010
00:52:07.500 --> 00:52:08.400
 as here.

1011
00:52:09.700 --> 00:52:12.000
and so the rest

1012
00:52:12.100 --> 00:52:13.300
 of the handshake

1013
00:52:14.500 --> 00:52:17.700
Is visible in here the rest of the handshake

1014
00:52:17.700 --> 00:52:21.100
 packets is visible in here.

1015
00:52:20.100 --> 00:52:24.100
 You can see this packet.

1016
00:52:25.100 --> 00:52:28.200
Is sent by the server and the other

1017
00:52:28.200 --> 00:52:32.000
 one is sent by the client and we

1018
00:52:31.300 --> 00:52:35.200
 can see these packets these handshake

1019
00:52:34.200 --> 00:52:36.400
 packets clearly.

1020
00:52:38.400 --> 00:52:41.900
But when we look at the other side, we only

1021
00:52:41.900 --> 00:52:44.600
 see the application data and the

1022
00:52:44.600 --> 00:52:48.800
 summarized information about packets

1023
00:52:47.800 --> 00:52:50.200
 about the TLs packets in

1024
00:52:50.200 --> 00:52:50.300
 here.

1025
00:52:51.100 --> 00:52:54.700
So you can see only the application data

1026
00:52:54.700 --> 00:52:57.000
 in here you can see.

1027
00:52:57.800 --> 00:52:59.000
And there is no more.

1028
00:52:59.900 --> 00:53:02.300
So you can see

1029
00:53:02.300 --> 00:53:05.800
 also the HTTP packets

1030
00:53:05.800 --> 00:53:06.100
 clearly.

1031
00:53:06.800 --> 00:53:09.700
You will see the HTTP as

1032
00:53:09.700 --> 00:53:10.700
 packets.

1033
00:53:12.100 --> 00:53:16.200
as the TLs packets as TRS packets

1034
00:53:15.200 --> 00:53:18.300
 TLS application data packets

1035
00:53:18.800 --> 00:53:22.400
And you can see the HTTP HTTP

1036
00:53:21.400 --> 00:53:23.800
 to packets in.

1037
00:53:24.600 --> 00:53:27.400
the encrypted traffic but you can

1038
00:53:27.400 --> 00:53:30.500
 see the HTTP two packets, which

1039
00:53:30.500 --> 00:53:32.600
 means HTTP s

1040
00:53:34.100 --> 00:53:38.700
which assigns the TLs encrypted TLS

1041
00:53:38.700 --> 00:53:42.300
 packets in the version HTTP

1042
00:53:41.300 --> 00:53:45.600
 2 you can see the http/2 packets

1043
00:53:45.600 --> 00:53:48.300
 in here clearly, but you can't see in

1044
00:53:48.300 --> 00:53:52.100
 the encrypted traffic then and

1045
00:53:53.100 --> 00:53:56.600
by sending the server certificate data in here.

1046
00:54:01.300 --> 00:54:04.300
By sending server certificate data. It says to

1047
00:54:04.300 --> 00:54:07.100
 the client. Hey, I am the server you are

1048
00:54:07.100 --> 00:54:10.800
 looking for and as you can see and Shake

1049
00:54:10.800 --> 00:54:12.200
 protocol extensions.

1050
00:54:15.400 --> 00:54:16.500
are encrypted

1051
00:54:17.200 --> 00:54:21.400
For example, we see that the LPN selection.

1052
00:54:22.800 --> 00:54:23.600
is in here

1053
00:54:24.600 --> 00:54:29.100
LPN selection in here HTTP

1054
00:54:27.100 --> 00:54:30.700
 HTTP tool

1055
00:54:31.200 --> 00:54:36.000
and the certificate data is given in compressed.

1056
00:54:36.800 --> 00:54:40.200
Mod in compressed format and

1057
00:54:39.200 --> 00:54:42.800
 we see that it uses the

1058
00:54:42.800 --> 00:54:45.500
 broadly algorithm for

1059
00:54:45.500 --> 00:54:48.100
 compressing which was offered by the

1060
00:54:48.100 --> 00:54:51.200
 client as a compressed option to the

1061
00:54:51.200 --> 00:54:51.900
 server.

1062
00:54:52.600 --> 00:54:54.500
and the following contains

1063
00:54:56.800 --> 00:55:00.100
necessary some some necessary

1064
00:54:59.100 --> 00:55:02.900
 information following data

1065
00:55:02.900 --> 00:55:07.000
 contains the necessary certificate information.

1066
00:55:06.800 --> 00:55:09.900
 We see the version and

1067
00:55:09.900 --> 00:55:12.200
 the serial number in here.

1068
00:55:15.300 --> 00:55:16.400
Let me show you.

1069
00:55:22.100 --> 00:55:25.600
in the shortcut field, you can

1070
00:55:25.600 --> 00:55:28.400
 see the version information and the serial

1071
00:55:28.400 --> 00:55:31.800
 number of the of this shortcut which

1072
00:55:31.800 --> 00:55:34.700
 is sent by the server and

1073
00:55:36.200 --> 00:55:37.100
on the other hand

1074
00:55:40.100 --> 00:55:44.900
here is the selected signature

1075
00:55:43.900 --> 00:55:46.400
 all your

1076
00:55:46.400 --> 00:55:47.600
 team in here.

1077
00:55:49.300 --> 00:55:50.500
the selected

1078
00:55:52.700 --> 00:55:55.800
the selected signature algorithm is

1079
00:55:55.800 --> 00:55:56.000
 in here.

1080
00:55:57.400 --> 00:56:02.200
We can see it and we will see important information

1081
00:56:01.200 --> 00:56:04.500
 about the validity of

1082
00:56:04.500 --> 00:56:07.800
 this certificate under the validity field.

1083
00:56:08.600 --> 00:56:11.400
So in here not before

1084
00:56:11.400 --> 00:56:14.600
 value and and not after value, let's talk

1085
00:56:14.600 --> 00:56:15.200
 about this.

1086
00:56:19.300 --> 00:56:21.400
In did not before section.

1087
00:56:22.300 --> 00:56:25.300
We see from which date this

1088
00:56:25.300 --> 00:56:26.900
 certificate is valid.

1089
00:56:27.500 --> 00:56:30.400
So time data in UTC time

1090
00:56:30.400 --> 00:56:33.800
 format format and it was

1091
00:56:33.800 --> 00:56:37.000
 a valid certificate as of that that

1092
00:56:36.000 --> 00:56:37.500
 date.

1093
00:56:38.600 --> 00:56:42.100
And here is the expired date

1094
00:56:41.100 --> 00:56:44.800
 in here is the

1095
00:56:44.800 --> 00:56:47.900
 expired date of shortcut and

1096
00:56:47.900 --> 00:56:51.400
 the end time is given under the

1097
00:56:51.400 --> 00:56:55.100
 not after field so

1098
00:56:54.100 --> 00:56:55.700
 and here.

1099
00:56:57.100 --> 00:56:59.500
We see the public key.

1100
00:57:00.700 --> 00:57:03.200
Failed also we can

1101
00:57:03.200 --> 00:57:07.700
 expand this window now again to see

1102
00:57:07.700 --> 00:57:09.900
 the clearly.

1103
00:57:12.300 --> 00:57:16.200
Okay, now we can also in here the

1104
00:57:15.200 --> 00:57:19.700
 on the another server message.

1105
00:57:23.700 --> 00:57:27.600
And before before the

1106
00:57:26.600 --> 00:57:29.800
 investigation of this packet,

1107
00:57:29.800 --> 00:57:33.600
 let's look at the inspiration for

1108
00:57:32.600 --> 00:57:34.600
 this packet.

1109
00:57:35.300 --> 00:57:39.000
First we have we have seen a

1110
00:57:38.600 --> 00:57:41.500
 decline Hello message from the client

1111
00:57:41.500 --> 00:57:44.200
 to the server side then.

1112
00:57:44.900 --> 00:57:49.200
the server sent its

1113
00:57:48.200 --> 00:57:51.600
 server Hello message with the

1114
00:57:51.600 --> 00:57:55.300
 same key share extension

1115
00:57:54.300 --> 00:57:58.500
 to make a key exchange

1116
00:57:57.500 --> 00:58:01.000
 process and a

1117
00:58:00.300 --> 00:58:04.700
 chosen Cipher Street it gave

1118
00:58:03.700 --> 00:58:07.500
 a anformation about

1119
00:58:09.500 --> 00:58:12.500
about its Cypher Suite that it

1120
00:58:12.500 --> 00:58:16.500
 has chosen and then we see

1121
00:58:15.500 --> 00:58:19.200
 the another packet after

1122
00:58:18.200 --> 00:58:21.400
 the server help message in

1123
00:58:21.400 --> 00:58:21.800
 here.

1124
00:58:22.500 --> 00:58:23.700
with this packed

1125
00:58:24.500 --> 00:58:27.800
you can see in here. Another packet

1126
00:58:27.800 --> 00:58:31.600
 is in here and it contains encrypted

1127
00:58:30.600 --> 00:58:33.900
 extensions and the

1128
00:58:33.900 --> 00:58:36.300
 compressed certificate and the sort of

1129
00:58:36.300 --> 00:58:38.200
 got verify and the finished.

1130
00:58:38.800 --> 00:58:41.900
So before this packet, we have

1131
00:58:41.900 --> 00:58:43.900
 a key exchange process.

1132
00:58:45.200 --> 00:58:48.900
By both client and the

1133
00:58:48.900 --> 00:58:49.400
 server side.

1134
00:58:50.200 --> 00:58:54.400
And after the key exchange process nor we

1135
00:58:53.400 --> 00:58:56.800
 have a process about

1136
00:58:56.800 --> 00:58:59.300
 the server perimeters and

1137
00:58:59.300 --> 00:59:00.900
 the Authentication.

1138
00:59:01.800 --> 00:59:05.300
So in this in at

1139
00:59:04.300 --> 00:59:09.000
 this point, the server will

1140
00:59:08.800 --> 00:59:11.700
 make a make an authentication

1141
00:59:11.700 --> 00:59:12.700
 about itself.

1142
00:59:14.300 --> 00:59:17.800
So and it will give the information about

1143
00:59:17.800 --> 00:59:21.800
 it sort of code and the other parameters in

1144
00:59:20.800 --> 00:59:24.500
 order to the

1145
00:59:23.500 --> 00:59:25.200
 client.

1146
00:59:27.600 --> 00:59:32.400
can can make an authentication that the

1147
00:59:31.400 --> 00:59:34.500
 server is the

1148
00:59:34.500 --> 00:59:38.000
 server is the true one is the is

1149
00:59:37.700 --> 00:59:41.000
 developed is the server that

1150
00:59:40.100 --> 00:59:44.200
 it is looking for and when we

1151
00:59:44.200 --> 00:59:48.400
 look at this packet, we have some another extensions

1152
00:59:47.400 --> 00:59:50.700
 in its so

1153
00:59:51.900 --> 00:59:55.700
Now let's turn back to the subject public

1154
00:59:54.700 --> 00:59:58.000
 key for area and

1155
00:59:57.600 --> 00:59:59.800
 when we look at this field.

1156
01:00:00.600 --> 01:00:03.500
We should say something about it.

1157
01:00:04.300 --> 01:00:05.300
and

1158
01:00:10.100 --> 01:00:13.300
we see the public K under this field

1159
01:00:13.300 --> 01:00:15.600
 as you can see in here.

1160
01:00:17.500 --> 01:00:21.100
The server also has its

1161
01:00:20.100 --> 01:00:24.300
 own public key information in

1162
01:00:23.300 --> 01:00:26.500
 here, but you can see this

1163
01:00:26.500 --> 01:00:30.400
 information within the encrypted

1164
01:00:29.400 --> 01:00:30.700
 traffic.

1165
01:00:31.600 --> 01:00:34.100
You can see this details.

1166
01:00:37.300 --> 01:00:41.100
Okay, and now we will look at the status request.

1167
01:00:42.200 --> 01:00:42.700
in here

1168
01:00:44.500 --> 01:00:46.200
the state's request

1169
01:00:52.700 --> 01:00:56.300
Let me find the status request extension

1170
01:00:55.300 --> 01:00:56.700
 in here.

1171
01:00:58.100 --> 01:00:59.900
And we will find.

1172
01:01:02.700 --> 01:01:02.800
the

1173
01:01:05.300 --> 01:01:06.900
status request

1174
01:01:11.600 --> 01:01:14.600
now we will talk about the state's request

1175
01:01:14.600 --> 01:01:15.500
 extension in here.

1176
01:01:16.300 --> 01:01:17.500
So as you can see.

1177
01:01:20.200 --> 01:01:24.000
We have some information about State circuits and

1178
01:01:23.700 --> 01:01:27.000
 maybe you can remember the client

1179
01:01:26.900 --> 01:01:29.400
 has been made a request

1180
01:01:29.400 --> 01:01:33.600
 about the status of the server certificate.

1181
01:01:33.600 --> 01:01:36.800
 And now the server is responding about

1182
01:01:36.800 --> 01:01:39.400
 its own status about its

1183
01:01:39.400 --> 01:01:42.700
 own certificate status to the

1184
01:01:42.700 --> 01:01:46.300
 client and the response

1185
01:01:45.300 --> 01:01:46.900
 is in.

1186
01:01:48.500 --> 01:01:52.000
Status request extension. So

1187
01:01:51.600 --> 01:01:55.000
 let's investigate the response now

1188
01:01:54.700 --> 01:01:57.300
 in here and

1189
01:01:58.600 --> 01:02:01.700
in status regards there is the response given

1190
01:02:01.700 --> 01:02:05.200
 by all CSP regarding the

1191
01:02:04.200 --> 01:02:08.600
 validity of the certificate. If

1192
01:02:08.600 --> 01:02:11.600
 you remember I have told you client request

1193
01:02:11.600 --> 01:02:14.800
 and answer from oscp protocol

1194
01:02:14.800 --> 01:02:17.500
 which means online certificates protocol

1195
01:02:17.500 --> 01:02:21.100
 whether the shortcut is valid or not. So here

1196
01:02:20.100 --> 01:02:23.300
 we can see the details of the

1197
01:02:23.300 --> 01:02:26.200
 answer and I am expanding the

1198
01:02:28.500 --> 01:02:29.100
in here

1199
01:02:30.400 --> 01:02:33.100
I'm expanding in here.

1200
01:02:33.700 --> 01:02:37.200
the TBS response data

1201
01:02:38.300 --> 01:02:41.900
in order to see the details about response about

1202
01:02:41.900 --> 01:02:45.700
 the response of the ocsp protocol

1203
01:02:45.700 --> 01:02:48.900
 and you can see the responder ID

1204
01:02:48.900 --> 01:02:51.700
 information and let's

1205
01:02:51.700 --> 01:02:53.100
 look at the responses.

1206
01:02:54.600 --> 01:02:55.200
field

1207
01:02:55.800 --> 01:02:58.300
we have a single response in

1208
01:02:58.300 --> 01:02:59.100
 here and

1209
01:03:00.400 --> 01:03:03.800
As you can see the certificate the certificate

1210
01:03:03.800 --> 01:03:04.900
 status is good.

1211
01:03:05.800 --> 01:03:09.100
So the ocsp protocol

1212
01:03:08.100 --> 01:03:12.700
 says that this certificate

1213
01:03:11.700 --> 01:03:15.100
 status is good to

1214
01:03:14.100 --> 01:03:15.800
 the client.

1215
01:03:16.800 --> 01:03:19.100
The ocsp says to the

1216
01:03:19.100 --> 01:03:23.200
 client. Hey, the server certificate

1217
01:03:22.200 --> 01:03:25.100
 States status is good.

1218
01:03:26.100 --> 01:03:27.100
So and

1219
01:03:28.100 --> 01:03:32.500
the status of the sort of cut validation

1220
01:03:33.500 --> 01:03:35.000
has an update time.

1221
01:03:35.600 --> 01:03:37.100
As you can see in here.

1222
01:03:37.900 --> 01:03:41.600
And we also see this update

1223
01:03:40.600 --> 01:03:43.900
 as the date these status

1224
01:03:43.900 --> 01:03:46.600
 information was issued in here.

1225
01:03:47.800 --> 01:03:50.900
And when we look at the next update.

1226
01:03:51.800 --> 01:03:54.100
We can see that it will be valid for.

1227
01:03:56.200 --> 01:03:59.400
7 days and the certificate States will

1228
01:03:59.400 --> 01:04:02.600
 be updated again on the date the

1229
01:04:02.600 --> 01:04:04.700
 next update date.

1230
01:04:05.200 --> 01:04:08.400
So you can find many more details about

1231
01:04:08.400 --> 01:04:12.400
 the certificate in here and to

1232
01:04:11.400 --> 01:04:15.300
 sum up the server shared its

1233
01:04:14.300 --> 01:04:17.800
 certificate with the client by sanding this

1234
01:04:17.800 --> 01:04:21.000
 encrypted normally

1235
01:04:20.400 --> 01:04:25.200
 in encrypted mode by

1236
01:04:23.200 --> 01:04:26.800
 sending this encrypted

1237
01:04:26.800 --> 01:04:29.600
 packet and said that hey

1238
01:04:29.600 --> 01:04:31.900
 I am the server you are looking for.

1239
01:04:33.300 --> 01:04:36.600
So the server shared its certificate

1240
01:04:36.600 --> 01:04:39.800
 to in order to say that.

1241
01:04:39.800 --> 01:04:42.100
 Hey, I am the server you are

1242
01:04:42.100 --> 01:04:42.800
 looking for.

1243
01:04:43.800 --> 01:04:46.400
And that includes a handshake finish

1244
01:04:46.400 --> 01:04:48.000
 message in here.

1245
01:04:49.400 --> 01:04:52.500
As you can see I finished message is

1246
01:04:52.500 --> 01:04:54.800
 in this packed.

1247
01:04:55.800 --> 01:04:59.200
And it means the handshake

1248
01:04:58.200 --> 01:05:00.700
 will be completed.

1249
01:05:01.700 --> 01:05:06.700
So let's turn back to the illustration. There

1250
01:05:05.700 --> 01:05:09.500
 is a finished message

1251
01:05:08.500 --> 01:05:11.800
 in our packet.

1252
01:05:13.400 --> 01:05:17.000
And we look at the next one the client also.

1253
01:05:19.100 --> 01:05:24.100
declined also will send another certificate verify

1254
01:05:23.100 --> 01:05:26.400
 message and the finished message

1255
01:05:26.400 --> 01:05:29.300
 as a packet and it will

1256
01:05:31.200 --> 01:05:35.100
check the authentication of

1257
01:05:34.100 --> 01:05:35.900
 the server.

1258
01:05:36.900 --> 01:05:40.500
By by checking the

1259
01:05:39.500 --> 01:05:43.800
 information that that

1260
01:05:43.800 --> 01:05:47.700
 is sent by the server in the

1261
01:05:47.700 --> 01:05:52.200
 in the previous packet. So and they

1262
01:05:51.200 --> 01:05:56.200
 send to each other change Cypher

1263
01:05:55.200 --> 01:05:58.800
 change Cypher

1264
01:05:58.800 --> 01:06:03.100
 message change. Sorry they

1265
01:06:02.100 --> 01:06:06.100
 sent to each other a change Cypher

1266
01:06:05.100 --> 01:06:09.000
 spec message which signals

1267
01:06:08.100 --> 01:06:12.000
 that their session case is being

1268
01:06:11.900 --> 01:06:15.300
 activated and you can

1269
01:06:15.300 --> 01:06:18.300
 see in here. The client is

1270
01:06:18.300 --> 01:06:23.000
 signing a change sign for

1271
01:06:22.300 --> 01:06:26.400
 spec message and it means

1272
01:06:26.400 --> 01:06:29.400
 and their session Keys

1273
01:06:29.400 --> 01:06:31.700
 is being activated so

1274
01:06:33.100 --> 01:06:36.300
The next packet is sent by the client to

1275
01:06:36.300 --> 01:06:40.200
 the server which contains a handshake finish message

1276
01:06:39.200 --> 01:06:41.000
 in here.

1277
01:06:43.400 --> 01:06:47.500
And this completes these companies

1278
01:06:47.500 --> 01:06:50.900
 the sorry and this completes.

1279
01:06:53.300 --> 01:06:56.700
And this completes the TLs

1280
01:06:56.700 --> 01:06:57.200
 handshake?

1281
01:06:58.800 --> 01:07:00.600
so by this message

1282
01:07:03.200 --> 01:07:07.800
the TLs handshake is being completed.

1283
01:07:08.600 --> 01:07:12.100
So now let's look at the next illustration.

1284
01:07:13.200 --> 01:07:16.900
At this point the TLs handshake is completed

1285
01:07:16.900 --> 01:07:17.100
 now.

1286
01:07:18.100 --> 01:07:18.700
Bye.

1287
01:07:20.900 --> 01:07:24.700
By the client is sending

1288
01:07:24.700 --> 01:07:27.400
 the last message the last

1289
01:07:27.400 --> 01:07:29.300
 TLS handshake message.

1290
01:07:30.200 --> 01:07:33.700
So we see after this

1291
01:07:33.700 --> 01:07:37.700
 stage data can be exchanged between

1292
01:07:36.700 --> 01:07:39.800
 the client and the server

1293
01:07:39.800 --> 01:07:42.900
 and we see data exchange

1294
01:07:42.900 --> 01:07:46.300
 as TLS version TLS version

1295
01:07:46.300 --> 01:07:49.500
 1.3 application data in

1296
01:07:49.500 --> 01:07:50.400
 network traffic.

1297
01:07:51.400 --> 01:07:51.800
You can see.

1298
01:07:54.500 --> 01:07:55.800
the application data

1299
01:07:57.200 --> 01:08:00.800
after the TLs handshake is completed.

1300
01:08:01.800 --> 01:08:05.300
so you can see these application data

1301
01:08:04.300 --> 01:08:06.400
 packets in the

1302
01:08:07.100 --> 01:08:10.700
Traffic on Wireshark also as well

1303
01:08:10.700 --> 01:08:13.800
 and as you can see after the

1304
01:08:13.800 --> 01:08:16.400
 TLs handshake there's an

1305
01:08:16.400 --> 01:08:17.300
 HTTP 2.

1306
01:08:18.200 --> 01:08:22.000
In the decrypted traffic we can see like that. We

1307
01:08:21.100 --> 01:08:25.200
 have an HTTP to packet in

1308
01:08:24.200 --> 01:08:28.500
 here and the server is sending

1309
01:08:27.500 --> 01:08:30.700
 a packet with the

1310
01:08:30.700 --> 01:08:33.700
 protocol HTTP to to the

1311
01:08:33.700 --> 01:08:35.200
 client then.

1312
01:08:37.300 --> 01:08:40.400
The client signing an

1313
01:08:40.400 --> 01:08:43.600
 egg message. Okay. I have received your

1314
01:08:43.600 --> 01:08:47.200
 http/2 packet, and then

1315
01:08:46.200 --> 01:08:49.600
 the client is

1316
01:08:49.600 --> 01:08:52.900
 sending another HTTP to message

1317
01:08:52.900 --> 01:08:55.900
 in here. So in this

1318
01:08:55.900 --> 01:08:57.800
 message, we can see

1319
01:08:58.800 --> 01:09:02.800
As clear text the hypertext

1320
01:09:01.800 --> 01:09:04.400
 transfer protocol data in

1321
01:09:04.400 --> 01:09:04.700
 here.

1322
01:09:05.600 --> 01:09:09.500
Empty after this http-2 messages

1323
01:09:08.500 --> 01:09:11.200
 declined is

1324
01:09:11.200 --> 01:09:14.400
 sending a get message and a

1325
01:09:14.400 --> 01:09:17.600
 HTTP get message get request message

1326
01:09:17.600 --> 01:09:20.400
 to the server as you can see in here,

1327
01:09:20.400 --> 01:09:24.100
 but you can't see these packets clearly

1328
01:09:23.100 --> 01:09:27.100
 without decrypting. Let's

1329
01:09:26.100 --> 01:09:27.700
 look at the

1330
01:09:28.900 --> 01:09:31.300
encrypted traffic in here

1331
01:09:32.200 --> 01:09:35.200
to the same packet the packet with the

1332
01:09:35.200 --> 01:09:36.400
 get a message.

1333
01:09:37.300 --> 01:09:41.000
Http/gate message is 72 and

1334
01:09:40.300 --> 01:09:44.000
 we can see this packet

1335
01:09:43.500 --> 01:09:46.400
 in clearly here. But when

1336
01:09:46.400 --> 01:09:49.100
 we look at the encrypted traffic.

1337
01:09:51.100 --> 01:09:53.000
to the same packet

1338
01:09:53.800 --> 01:09:54.600
72

1339
01:09:55.900 --> 01:09:56.700
You can see.

1340
01:09:57.800 --> 01:10:01.600
The protocol is TLS version 1.3.

1341
01:10:00.600 --> 01:10:04.000
 Not the HTTP 2.

1342
01:10:03.200 --> 01:10:05.900
 We don't know.

1343
01:10:08.300 --> 01:10:11.000
Which protocol is used in here?

1344
01:10:12.400 --> 01:10:15.600
HTTP or another one? We we don't

1345
01:10:15.600 --> 01:10:19.000
 have this information in here because this

1346
01:10:18.600 --> 01:10:21.700
 packet is encrypted by the trailers.

1347
01:10:22.500 --> 01:10:25.400
And we can see only the

1348
01:10:25.400 --> 01:10:29.100
 protocol TLS version 1.3 and

1349
01:10:28.100 --> 01:10:31.600
 as data we can see only the

1350
01:10:31.600 --> 01:10:32.700
 application data.

1351
01:10:33.300 --> 01:10:36.100
Information there is no more in here.

1352
01:10:36.100 --> 01:10:40.700
 But when we look at the traffic that that

1353
01:10:40.700 --> 01:10:44.100
 has been decrypted before

1354
01:10:43.100 --> 01:10:46.100
 we can we can see

1355
01:10:46.100 --> 01:10:49.100
 this packet we can

1356
01:10:49.100 --> 01:10:52.700
 see that this packet is an is an HTTP 2 packet

1357
01:10:52.700 --> 01:10:55.200
 and it is a it is

1358
01:10:55.200 --> 01:10:57.000
 a get request packet.

1359
01:10:57.800 --> 01:11:00.800
And okay, then we can

1360
01:11:00.800 --> 01:11:03.200
 investigate the rest of

1361
01:11:03.200 --> 01:11:03.900
 the traffic.

1362
01:11:05.200 --> 01:11:06.000
In this way.

1363
01:11:07.100 --> 01:11:08.800
and we can see the

1364
01:11:10.400 --> 01:11:11.400
other packs

1365
01:11:13.700 --> 01:11:16.600
so that's all about the TLs handshake careless

1366
01:11:16.600 --> 01:11:19.900
 version 1.3 and shape process.

1367
01:11:21.200 --> 01:11:24.400
And we will investigate the decision of

1368
01:11:24.400 --> 01:11:28.900
 of the http/s protocol on

1369
01:11:28.900 --> 01:11:29.800
 the next lesson.

1370
01:11:33.300 --> 01:11:34.800
That's all for now.

1371
01:11:35.500 --> 01:11:36.700
See you on the next video.
