WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.500 --> 00:00:10.800
Hello everyone in this lesson. I will tell you the FTP

1
00:00:10.800 --> 00:00:11.500
 analysis.

2
00:00:15.300 --> 00:00:18.200
So before starting to analyze let's talk

3
00:00:18.200 --> 00:00:20.300
 about the FTP protocol for a while.

4
00:00:21.400 --> 00:00:23.000
while transfer protocol

5
00:00:23.800 --> 00:00:26.600
As you know ATP is a

6
00:00:26.600 --> 00:00:29.500
 standard Network protocol user to transfer files from

7
00:00:29.500 --> 00:00:32.600
 one horse to another over a tcp-based network

8
00:00:32.600 --> 00:00:36.300
 such as the internet FTP is

9
00:00:36.300 --> 00:00:40.000
 built on a client server architecture and

10
00:00:39.300 --> 00:00:42.400
 use a separate control

11
00:00:42.400 --> 00:00:45.800
 and data connections between the client and the

12
00:00:45.800 --> 00:00:48.700
 server when a client initiates an

13
00:00:48.700 --> 00:00:51.700
 FTP session it established control

14
00:00:51.700 --> 00:00:54.500
 connection with the server the client then

15
00:00:54.500 --> 00:00:58.100
 sends commands such as requesting a directory this

16
00:00:57.100 --> 00:01:00.300
 thing or uploading a file

17
00:01:00.300 --> 00:01:03.700
 over this connection the server response

18
00:01:03.700 --> 00:01:06.700
 to these commands and send status

19
00:01:06.700 --> 00:01:09.100
 and error messages back to the client.

20
00:01:10.200 --> 00:01:13.300
So for file transfers is separate

21
00:01:13.300 --> 00:01:16.500
 data connection is established between the client and

22
00:01:16.500 --> 00:01:19.500
 server the client initiates the

23
00:01:19.500 --> 00:01:22.500
 transfer by sending a command

24
00:01:22.500 --> 00:01:26.300
 over the control connection such as retrieve

25
00:01:25.300 --> 00:01:28.900
 to download a file as

26
00:01:28.900 --> 00:01:31.700
 retr or store

27
00:01:31.700 --> 00:01:36.000
 as St. Or to upload

28
00:01:35.000 --> 00:01:36.900
 file.

29
00:01:37.700 --> 00:01:40.600
The server then sends or receives the

30
00:01:40.600 --> 00:01:45.000
 file over the data connection and FTP

31
00:01:43.600 --> 00:01:46.900
 uses two main modes

32
00:01:46.900 --> 00:01:48.200
 of file transfer.

33
00:01:48.900 --> 00:01:52.300
First one is asking mode and binary

34
00:01:51.300 --> 00:01:54.300
 and the second one is binary mode

35
00:01:54.300 --> 00:01:58.200
 asking mode is used for text

36
00:01:57.200 --> 00:02:01.200
 files and translates line

37
00:02:00.200 --> 00:02:03.800
 ending characters between different

38
00:02:03.800 --> 00:02:06.200
 platforms binary mode is

39
00:02:06.200 --> 00:02:09.700
 used for all other file types and doesn't

40
00:02:09.700 --> 00:02:11.600
 perform any translations.

41
00:02:12.300 --> 00:02:15.700
So FTP is a widely used protocol

42
00:02:15.700 --> 00:02:19.100
 for transferring files, but it has some security

43
00:02:18.100 --> 00:02:22.400
 issues. For example, it sends

44
00:02:22.400 --> 00:02:25.900
 login credentials in plain

45
00:02:25.900 --> 00:02:29.700
 text and which can be intercepted by

46
00:02:29.700 --> 00:02:32.500
 attackers. And therefore it

47
00:02:32.500 --> 00:02:36.400
 is recommended to use secure file transfer protocols

48
00:02:35.400 --> 00:02:38.700
 such as SFTP or

49
00:02:38.700 --> 00:02:41.900
 FTP over SSL TLS.

50
00:02:41.900 --> 00:02:44.900
 And now let's investigate

51
00:02:44.900 --> 00:02:46.100
 APK file.

52
00:02:46.800 --> 00:02:48.700
We have a PK file.

53
00:02:49.500 --> 00:02:53.100
associated with FTP protocol and

54
00:02:52.100 --> 00:02:55.200
 FTP Network traffic

55
00:02:56.500 --> 00:02:59.600
and in here first, we should

56
00:02:59.600 --> 00:03:03.200
 know that we only need to type FTP

57
00:03:02.200 --> 00:03:04.200
 as a filter.

58
00:03:05.100 --> 00:03:06.800
in the display filter field

59
00:03:09.600 --> 00:03:12.900
and you need to type FTP

60
00:03:12.900 --> 00:03:15.800
 as a filter to see only FTP packets

61
00:03:15.800 --> 00:03:17.300
 in our pickup file.

62
00:03:18.200 --> 00:03:19.300
And click on the enter.

63
00:03:20.600 --> 00:03:23.800
as you can see now we have only

64
00:03:23.800 --> 00:03:24.900
 the

65
00:03:25.800 --> 00:03:27.600
FTP packets

66
00:03:29.800 --> 00:03:32.500
And we will apply another.

67
00:03:33.400 --> 00:03:36.900
Filtering expression and this filtering

68
00:03:36.900 --> 00:03:40.500
 is like the this FTP dot

69
00:03:40.500 --> 00:03:41.800
 request.

70
00:03:44.600 --> 00:03:44.900
and

71
00:03:46.500 --> 00:03:46.900
Dot

72
00:03:49.500 --> 00:03:50.100
comment

73
00:03:51.600 --> 00:03:55.100
Ftp.workers dot command, this filter

74
00:03:54.100 --> 00:03:58.200
 brings us the commands used

75
00:03:57.200 --> 00:04:00.400
 in the requests made to

76
00:04:00.400 --> 00:04:03.300
 the FTP server. For example, we can

77
00:04:03.300 --> 00:04:06.200
 use in this filtering we can

78
00:04:06.200 --> 00:04:09.600
 use user command from FTP commands

79
00:04:09.600 --> 00:04:12.200
 to analyze users trying to

80
00:04:12.200 --> 00:04:15.700
 login to FTP server for this. It

81
00:04:15.700 --> 00:04:19.800
 is enough to make a small change in our filter

82
00:04:18.800 --> 00:04:22.600
 and we can add the

83
00:04:21.600 --> 00:04:23.200
 command.

84
00:04:24.600 --> 00:04:27.900
that we want to see the packets associated

85
00:04:27.900 --> 00:04:30.800
 with it and in here you can

86
00:04:30.800 --> 00:04:33.300
 type the command as

87
00:04:34.600 --> 00:04:35.100
user

88
00:04:35.800 --> 00:04:38.700
So now we want to see the

89
00:04:38.700 --> 00:04:42.600
 packets which has been applied

90
00:04:41.600 --> 00:04:44.900
 user command and when

91
00:04:44.900 --> 00:04:46.500
 we click on the enter.

92
00:04:48.900 --> 00:04:51.700
As you see in here now, we

93
00:04:51.700 --> 00:04:54.900
 have only the packets which

94
00:04:54.900 --> 00:04:57.600
 is used which is applied a

95
00:04:57.600 --> 00:04:58.200
 user command.

96
00:04:59.200 --> 00:05:00.500
and in here

97
00:05:01.600 --> 00:05:04.200
it brought all packets associated with

98
00:05:04.200 --> 00:05:07.100
 the user command and FTP commands are

99
00:05:07.100 --> 00:05:09.100
 sent to the server.

100
00:05:10.200 --> 00:05:13.700
FTP commands are sent to the server as plain

101
00:05:13.700 --> 00:05:16.300
 text and the server reply also in

102
00:05:16.300 --> 00:05:17.300
 plain text.

103
00:05:17.900 --> 00:05:20.700
So remind that keep in mind that and some

104
00:05:20.700 --> 00:05:24.000
 common FTP commands like

105
00:05:23.400 --> 00:05:25.500
 this, let me show you.

106
00:05:26.700 --> 00:05:28.300
in another screen

107
00:05:33.100 --> 00:05:36.100
So you see the FTP commands in

108
00:05:36.100 --> 00:05:39.500
 here and first one is user and

109
00:05:39.500 --> 00:05:43.300
 pass commands there for

110
00:05:42.300 --> 00:05:45.300
 authentication process as you

111
00:05:45.300 --> 00:05:47.300
 guess user.

112
00:05:47.800 --> 00:05:51.100
Is used to enter the username and

113
00:05:50.100 --> 00:05:54.000
 pass command is

114
00:05:53.300 --> 00:05:57.200
 used to enter the password information

115
00:05:56.200 --> 00:06:00.900
 and PWD is

116
00:06:00.900 --> 00:06:04.100
 used to display the current working directory

117
00:06:03.100 --> 00:06:06.300
 on the server. And the other one is

118
00:06:07.200 --> 00:06:11.100
commonly used and CWD is

119
00:06:10.100 --> 00:06:14.000
 used to change the current working

120
00:06:13.700 --> 00:06:16.700
 director on the server and least

121
00:06:16.700 --> 00:06:19.300
 command is used to display a list

122
00:06:19.300 --> 00:06:22.500
 of files in the current directory on the server.

123
00:06:22.500 --> 00:06:25.500
 So the retrieve command

124
00:06:25.500 --> 00:06:28.400
 are ETR is used

125
00:06:28.400 --> 00:06:31.700
 to download a file from the server and the

126
00:06:31.700 --> 00:06:34.300
 store is used to upload a

127
00:06:34.300 --> 00:06:37.200
 file to the server and there is

128
00:06:37.200 --> 00:06:40.300
 a delete command which is

129
00:06:40.300 --> 00:06:43.600
 used to delete a file on the server.

130
00:06:44.900 --> 00:06:47.300
So the last one is last one

131
00:06:47.300 --> 00:06:51.000
 is create a command and it is used to close the

132
00:06:50.900 --> 00:06:52.200
 FTP session.

133
00:06:53.200 --> 00:06:57.100
And now let's continue to investigate in

134
00:06:56.100 --> 00:06:58.200
 our PK file.

135
00:07:01.500 --> 00:07:05.100
You can also use that filter. I'm gonna

136
00:07:04.100 --> 00:07:08.200
 show you to detect attacks such

137
00:07:08.200 --> 00:07:12.000
 as Brute Force login attack and you

138
00:07:11.500 --> 00:07:14.400
 can use that command to

139
00:07:14.400 --> 00:07:17.400
 investigate the Brute Force

140
00:07:17.400 --> 00:07:18.000
 attacks.

141
00:07:19.200 --> 00:07:22.600
Now we are typing our filter expression.

142
00:07:24.800 --> 00:07:25.700
FTP Dot

143
00:07:26.200 --> 00:07:27.100
response

144
00:07:29.500 --> 00:07:30.000
and that

145
00:07:30.800 --> 00:07:31.300
code

146
00:07:33.100 --> 00:07:34.300
and is equal to

147
00:07:35.700 --> 00:07:36.100
5

148
00:07:38.600 --> 00:07:39.100
30

149
00:07:40.600 --> 00:07:43.800
so this number is our Response Code

150
00:07:43.800 --> 00:07:46.600
 number Response Code value.

151
00:07:47.600 --> 00:07:50.400
And since these Response Code

152
00:07:50.400 --> 00:07:54.400
 returns a failed login attempts, we

153
00:07:53.400 --> 00:07:56.300
 can analyze whether there are

154
00:07:56.300 --> 00:07:59.700
 attack patterns and in very

155
00:07:59.700 --> 00:08:02.100
 short time periods. It can be

156
00:08:02.100 --> 00:08:06.700
 investigated whether there is an attack by evaluating many

157
00:08:05.700 --> 00:08:08.300
 aspects such as

158
00:08:08.300 --> 00:08:11.900
 too many unsuccessful password entries or

159
00:08:11.900 --> 00:08:14.200
 if the source IP is

160
00:08:14.200 --> 00:08:17.100
 suspicious. So let's click on

161
00:08:17.100 --> 00:08:17.700
 the enter.

162
00:08:18.600 --> 00:08:21.600
And we have in here a few

163
00:08:21.600 --> 00:08:25.000
 packet with the response

164
00:08:24.400 --> 00:08:27.300
 code 530.

165
00:08:27.800 --> 00:08:31.300
And as you can see in here this type

166
00:08:30.300 --> 00:08:32.900
 of response.

167
00:08:34.200 --> 00:08:38.600
Is showing us the incorrect password packets, which

168
00:08:38.600 --> 00:08:40.400
 means not locked in.

169
00:08:41.200 --> 00:08:45.000
So there is a statement with incorrect

170
00:08:44.000 --> 00:08:45.400
 password.

171
00:08:47.200 --> 00:08:51.500
And we can analyze some attempts some

172
00:08:51.500 --> 00:08:53.600
 login attempts in this way.

173
00:08:56.100 --> 00:09:00.200
So now let's look at the another PK file.

174
00:09:09.400 --> 00:09:12.900
You can use the FTP even data

175
00:09:12.900 --> 00:09:16.600
 filter to see the transfer data.

176
00:09:16.600 --> 00:09:19.900
 You can use I mean this filter

177
00:09:19.900 --> 00:09:22.500
 FTP here from

178
00:09:23.300 --> 00:09:23.700
data

179
00:09:24.800 --> 00:09:25.000
so

180
00:09:25.800 --> 00:09:28.400
you can use this filter to see

181
00:09:28.400 --> 00:09:31.500
 the transfer data with this

182
00:09:31.500 --> 00:09:35.200
 filter. You will see the data downloaded with retrieve

183
00:09:34.200 --> 00:09:37.700
 command and upload it to the server

184
00:09:37.700 --> 00:09:41.000
 with Stockman. So now let's

185
00:09:40.700 --> 00:09:42.500
 click on the enter.

186
00:09:43.300 --> 00:09:47.800
And as you can see in here some data

187
00:09:46.800 --> 00:09:48.800
 packets via.

188
00:09:49.400 --> 00:09:50.700
FTP protocol

189
00:09:51.400 --> 00:09:54.900
and you can see the retrieved command.

190
00:09:56.100 --> 00:09:58.100
in the first packets

191
00:09:59.100 --> 00:10:03.600
And you can also see the packets with

192
00:10:03.600 --> 00:10:04.900
 store command.

193
00:10:05.800 --> 00:10:05.900
So

194
00:10:07.200 --> 00:10:07.800
in here

195
00:10:08.800 --> 00:10:11.600
Wireshark also allows you

196
00:10:11.600 --> 00:10:11.600
 to

197
00:10:13.500 --> 00:10:16.500
why shall also allows you to

198
00:10:16.500 --> 00:10:19.400
 follow the TCP stream of a specific

199
00:10:19.400 --> 00:10:22.500
 packet and this can be useful when

200
00:10:22.500 --> 00:10:25.500
 analyzing the data transfer to follow the

201
00:10:25.500 --> 00:10:27.000
 TCP stream.

202
00:10:28.600 --> 00:10:28.900
You can.

203
00:10:30.400 --> 00:10:33.900
Right click on a packet and select

204
00:10:33.900 --> 00:10:37.100
 follow then TCP stream.

205
00:10:38.400 --> 00:10:39.700
and you will see the

206
00:10:42.100 --> 00:10:46.400
the TCP stream which is associated the

207
00:10:45.400 --> 00:10:49.000
 packet that you have selected. So

208
00:10:48.800 --> 00:10:51.700
 there is a TCP stream

209
00:10:51.700 --> 00:10:55.000
 with Tom FTP data.

210
00:10:57.300 --> 00:11:00.800
And you can follow the FTP stream in

211
00:11:00.800 --> 00:11:01.300
 this way.

212
00:11:02.800 --> 00:11:06.600
You can investigate the data

213
00:11:05.600 --> 00:11:08.500
 packets in

214
00:11:08.500 --> 00:11:08.800
 here.

215
00:11:13.600 --> 00:11:16.300
And now we can close this screen.

216
00:11:21.300 --> 00:11:24.200
And I will cancel this filtering.

217
00:11:25.700 --> 00:11:29.500
I want to just type the FTP

218
00:11:28.500 --> 00:11:30.300
 command and

219
00:11:31.300 --> 00:11:34.000
in order to obtain

220
00:11:37.500 --> 00:11:41.400
better conversation stream associated

221
00:11:40.400 --> 00:11:43.300
 with the FTP protocol

222
00:11:44.100 --> 00:11:48.000
for example, let's select this packet and

223
00:11:49.300 --> 00:11:53.500
When you click on the follow anticipate stream.

224
00:11:54.200 --> 00:11:54.700
like this

225
00:11:55.500 --> 00:11:58.200
that is what I want and what I want

226
00:11:58.200 --> 00:12:01.200
 to show you and as you can see in here.

227
00:12:02.600 --> 00:12:06.500
there is a FTP stream FTP

228
00:12:05.500 --> 00:12:09.200
 conversation and firstly

229
00:12:08.200 --> 00:12:12.000
 there is a user login

230
00:12:11.000 --> 00:12:12.900
 as

231
00:12:13.600 --> 00:12:16.000
Anonymous and then

232
00:12:17.400 --> 00:12:20.100
we can see in here password information.

233
00:12:21.100 --> 00:12:24.100
And the there's a command.

234
00:12:24.700 --> 00:12:28.000
Nftp command CWD.

235
00:12:29.100 --> 00:12:29.500
and

236
00:12:30.500 --> 00:12:30.900
so on.

237
00:12:31.800 --> 00:12:32.600
so here

238
00:12:34.300 --> 00:12:37.700
a file is downloaded which is

239
00:12:37.700 --> 00:12:41.200
 called Excalibur that hqx

240
00:12:40.200 --> 00:12:43.200
 extension. You can

241
00:12:43.200 --> 00:12:44.800
 see in here and

242
00:12:47.400 --> 00:12:51.000
there is an another file which is uploaded

243
00:12:50.200 --> 00:12:53.100
 to the server with this name.

244
00:12:54.200 --> 00:12:58.400
So you can see the all the entire FTP communication

245
00:12:57.400 --> 00:13:01.000
 FTP stream in

246
00:13:00.400 --> 00:13:04.300
 this window and you can investigate all

247
00:13:03.300 --> 00:13:07.200
 the FTP traffic.

248
00:13:09.300 --> 00:13:13.800
So this is history is really useful window

249
00:13:13.800 --> 00:13:16.300
 to analyze the FTP traffic.

250
00:13:18.400 --> 00:13:20.400
Now we can close this window.

251
00:13:25.500 --> 00:13:25.600
and

252
00:13:28.100 --> 00:13:31.000
another useful tool in Wireshark

253
00:13:31.600 --> 00:13:34.100
In order to see the file contents in

254
00:13:34.100 --> 00:13:37.500
 clear text you can use the Wireshark built-in

255
00:13:37.500 --> 00:13:40.600
 feature as I as I

256
00:13:40.600 --> 00:13:44.300
 told you before and this

257
00:13:43.300 --> 00:13:46.700
 feature is export objects.

258
00:13:46.700 --> 00:13:49.400
 Maybe you can guess in

259
00:13:49.400 --> 00:13:51.800
 here under the file menu.

260
00:13:52.600 --> 00:13:55.500
You will go to the export objects and

261
00:13:55.500 --> 00:13:59.100
 you can choose the FTP data.

262
00:13:58.100 --> 00:14:02.700
 So in here the data.

263
00:14:04.400 --> 00:14:08.100
Which has been seen in the FTP traffic

264
00:14:07.100 --> 00:14:11.400
 you can choose the file that

265
00:14:10.400 --> 00:14:13.600
 you want to export and then you

266
00:14:13.600 --> 00:14:16.600
 can choose the save button and you

267
00:14:16.600 --> 00:14:19.900
 can investigate in detail these

268
00:14:19.900 --> 00:14:20.400
 files.

269
00:14:21.600 --> 00:14:24.600
And you can analyze them whether there

270
00:14:24.600 --> 00:14:27.400
 is a suspicious patterns and you

271
00:14:27.400 --> 00:14:30.400
 can use this window to make

272
00:14:30.400 --> 00:14:32.000
 these analysis.

273
00:14:34.900 --> 00:14:35.000
So

274
00:14:37.100 --> 00:14:40.600
you can use this tool this Wireshark tool

275
00:14:40.600 --> 00:14:43.500
 to obtain the file that

276
00:14:43.500 --> 00:14:44.900
 you want to export.

277
00:14:46.700 --> 00:14:48.400
And we can close now.

278
00:14:50.100 --> 00:14:53.900
And you can look for some suspicious commands such

279
00:14:53.900 --> 00:14:56.500
 as chmod command which

280
00:14:56.500 --> 00:14:59.500
 is used to change the executing permissions of a

281
00:14:59.500 --> 00:15:02.700
 file. As you know, chmod command

282
00:15:02.700 --> 00:15:05.900
 is used to change the permissions of

283
00:15:05.900 --> 00:15:08.800
 a file and in order to find and look

284
00:15:08.800 --> 00:15:12.000
 for suspicious FTP data commands. You

285
00:15:11.200 --> 00:15:15.000
 can use the FTP hidden

286
00:15:14.000 --> 00:15:16.900
 data parameters.

287
00:15:17.800 --> 00:15:19.200
again, we will use

288
00:15:20.100 --> 00:15:23.700
the FTP Heaven data filter

289
00:15:23.700 --> 00:15:27.000
 expression FTP even

290
00:15:26.800 --> 00:15:30.500
 and data then we

291
00:15:29.500 --> 00:15:33.000
 will add another perimeter

292
00:15:32.300 --> 00:15:35.600
 in here that command.

293
00:15:38.100 --> 00:15:41.400
And in here we will write the filter

294
00:15:41.400 --> 00:15:44.600
 like this. Let's suppose

295
00:15:44.600 --> 00:15:47.300
 that we are looking for whether there is a

296
00:15:47.300 --> 00:15:50.300
 CH command. So then we write this filter.

297
00:15:53.600 --> 00:15:54.100
Sorry.

298
00:15:57.900 --> 00:16:00.900
FTP data that

299
00:16:00.900 --> 00:16:02.300
 command

300
00:16:03.400 --> 00:16:05.300
is equal to

301
00:16:07.500 --> 00:16:08.000
Ch.

302
00:16:09.200 --> 00:16:09.800
node

303
00:16:12.100 --> 00:16:12.300
so

304
00:16:13.400 --> 00:16:14.600
let's click on the enter.

305
00:16:15.900 --> 00:16:19.900
And as you can see, there is no packet with

306
00:16:19.900 --> 00:16:22.600
 chmod command which contains

307
00:16:22.600 --> 00:16:25.400
 Sage Mode commands. There is

308
00:16:25.400 --> 00:16:29.100
 no packet with this command. So or we

309
00:16:28.100 --> 00:16:32.100
 can write that to find

310
00:16:31.100 --> 00:16:34.400
 out whether there is

311
00:16:34.400 --> 00:16:37.600
 a packet with this command and you

312
00:16:37.600 --> 00:16:40.500
 can use these filter again.

313
00:16:42.600 --> 00:16:46.600
Ftpdata dot command matches. Maybe

314
00:16:45.600 --> 00:16:48.000
 you will remember this.

315
00:16:50.500 --> 00:16:51.300
and command

316
00:16:52.500 --> 00:16:55.100
is chm mode again.

317
00:16:55.800 --> 00:16:58.100
You can use this way.

318
00:16:59.900 --> 00:17:03.000
To in order to find the packets with

319
00:17:02.300 --> 00:17:05.400
 this command as well.

320
00:17:05.400 --> 00:17:09.000
 So when we click on the enter, the

321
00:17:08.500 --> 00:17:11.400
 result will be the same of course

322
00:17:11.400 --> 00:17:15.100
 and so there is no packet usage

323
00:17:14.100 --> 00:17:17.500
 mode command in and now let's

324
00:17:17.500 --> 00:17:21.000
 change this command to list.

325
00:17:23.600 --> 00:17:24.400
let's look at

326
00:17:26.300 --> 00:17:26.800
this command

327
00:17:28.300 --> 00:17:30.600
and click on the enter as you can see.

328
00:17:32.200 --> 00:17:36.100
There are a few files if you packets with

329
00:17:35.100 --> 00:17:37.300
 list command.

330
00:17:38.200 --> 00:17:38.400
and

331
00:17:39.600 --> 00:17:42.900
this command is used in these packets.

332
00:17:44.200 --> 00:17:47.700
And you can create your filters, of course.

333
00:17:49.500 --> 00:17:53.700
using the packet details information

334
00:17:54.800 --> 00:17:57.700
so we want to create our filtering

335
00:17:57.700 --> 00:18:00.300
 with the command parameter, so

336
00:18:01.400 --> 00:18:04.300
To do this we can use this perimeter in here.

337
00:18:05.500 --> 00:18:07.600
And you can right click.

338
00:18:08.500 --> 00:18:11.900
Then prepare as filter and select

339
00:18:11.900 --> 00:18:12.200
 it.

340
00:18:13.400 --> 00:18:14.000
as you can see

341
00:18:15.500 --> 00:18:17.900
it is applied directly.

342
00:18:19.000 --> 00:18:19.300
so

343
00:18:22.400 --> 00:18:26.400
this is the another way to create your filtering

344
00:18:25.400 --> 00:18:27.400
 expressions.

345
00:18:31.500 --> 00:18:35.100
Okay, that's all about FTP protocol

346
00:18:34.100 --> 00:18:36.500
 see on the next video.
