WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.500 --> 00:00:10.200
Hi and welcome back to section 1 net get

1
00:00:10.200 --> 00:00:10.800
 introduction.

2
00:00:11.400 --> 00:00:14.900
In this video, we will explore base cooperations

3
00:00:14.900 --> 00:00:17.500
 with netcat in some different situations.

4
00:00:18.700 --> 00:00:21.300
Netcat is a network program designing to

5
00:00:21.300 --> 00:00:24.800
 read and write data across connections and following

6
00:00:24.800 --> 00:00:28.200
 this principle. We can enumerate scenarios in

7
00:00:27.200 --> 00:00:30.400
 that netcat is able to be used

8
00:00:30.400 --> 00:00:34.400
 like simple short interface Parts scanning

9
00:00:34.400 --> 00:00:36.500
 transferring the files.

10
00:00:37.500 --> 00:00:38.800
burner grabbing

11
00:00:39.400 --> 00:00:41.500
redirecting ports and traffic

12
00:00:42.600 --> 00:00:45.500
for a simple shot interface that can be

13
00:00:45.500 --> 00:00:48.600
 used on the same computer or on

14
00:00:48.600 --> 00:00:49.500
 different computers.

15
00:00:50.700 --> 00:00:53.700
For pot scanning netcat is not the best optional

16
00:00:53.700 --> 00:00:54.900
 way before this operation.

17
00:00:55.700 --> 00:00:58.200
For example netmap is the best tool for

18
00:00:58.200 --> 00:01:02.200
 this Mission, but netcat can be used for basic

19
00:01:01.200 --> 00:01:03.000
 Port scanning.

20
00:01:04.100 --> 00:01:07.500
For transferring files. Netcat has the ability

21
00:01:07.500 --> 00:01:10.200
 to both pool and push files.

22
00:01:11.100 --> 00:01:12.300
in binary grabbing

23
00:01:13.200 --> 00:01:16.500
is a enumeration technique which is designed to

24
00:01:16.500 --> 00:01:19.800
 determine the brain version operating system

25
00:01:19.800 --> 00:01:22.600
 or other relevant information about

26
00:01:22.600 --> 00:01:25.000
 a particular service or application.

27
00:01:26.100 --> 00:01:29.800
Redirecting ports and traffic is very useful. If

28
00:01:29.800 --> 00:01:32.400
 you want to obscure the source of an attack.

29
00:01:32.400 --> 00:01:35.400
 The idea here is to run netcat through a

30
00:01:35.400 --> 00:01:39.300
 middleman so that the attack appears to

31
00:01:39.300 --> 00:01:42.600
 be coming from the middleman and not the

32
00:01:42.600 --> 00:01:46.400
 original Source these reduction of traffic

33
00:01:45.400 --> 00:01:47.800
 is called a relay.

34
00:01:49.800 --> 00:01:52.100
In a simple shock interface. We will

35
00:01:52.100 --> 00:01:55.800
 simulate a simple shot communication from one

36
00:01:55.800 --> 00:01:59.000
 side. We will run netcat in several

37
00:01:58.900 --> 00:02:01.500
 mode when I open door 1 2 3

38
00:02:01.500 --> 00:02:01.900
 4 5

39
00:02:02.600 --> 00:02:05.400
And on the other side, we will run

40
00:02:05.400 --> 00:02:07.900
 a netcat instance to connect minister.

41
00:02:08.700 --> 00:02:11.700
After the conditions done. Both Siders are

42
00:02:11.700 --> 00:02:14.400
 able to exchange text as a shot

43
00:02:14.400 --> 00:02:15.100
 server.

44
00:02:17.300 --> 00:02:20.800
So in a server we will run Isis mean netcat.

45
00:02:25.800 --> 00:02:28.500
So in this example unit cakes netcat is

46
00:02:28.500 --> 00:02:28.800
 running.

47
00:02:29.400 --> 00:02:32.400
in the Mina L option

48
00:02:32.400 --> 00:02:33.000
 for listen

49
00:02:34.200 --> 00:02:37.400
using a p option for

50
00:02:37.400 --> 00:02:40.400
 open or specific door.

51
00:02:40.400 --> 00:02:43.400
 So in this instance here netcat is able and

52
00:02:43.400 --> 00:02:44.800
 running in a server mode.

53
00:02:45.500 --> 00:02:49.000
And it is extends here. We will start netget as

54
00:02:48.300 --> 00:02:49.400
 a client.

55
00:02:54.500 --> 00:02:57.600
So the connection is done. So now we

56
00:02:57.600 --> 00:03:00.700
 have a link between these two these two

57
00:03:00.700 --> 00:03:03.600
 instance of that cat. So for example

58
00:03:03.600 --> 00:03:04.800
 in one side you say

59
00:03:08.300 --> 00:03:11.900
and can see the text are exchanging from

60
00:03:11.900 --> 00:03:13.200
 one side to another.

61
00:03:24.100 --> 00:03:26.000
So the connection is done.

62
00:03:26.900 --> 00:03:29.800
And remembering that all connections using netcat

63
00:03:29.800 --> 00:03:32.900
 are unacrypted and we so

64
00:03:32.900 --> 00:03:36.300
 you will see in the future in the next session another to

65
00:03:35.300 --> 00:03:38.700
 call cryptkat that incorporate

66
00:03:38.700 --> 00:03:41.300
 and keep it toners and makes the

67
00:03:41.300 --> 00:03:42.300
 connection more safe.

68
00:03:46.900 --> 00:03:49.500
import scanning some options used

69
00:03:49.500 --> 00:03:51.300
 for this operation are

70
00:03:53.600 --> 00:03:57.600
-w or networking activity timeout Dash

71
00:03:56.600 --> 00:03:59.200
 Z or get the

72
00:03:59.200 --> 00:04:02.200
 status board - I or set

73
00:04:02.200 --> 00:04:06.000
 a delay interval between Port scanning and that's

74
00:04:05.300 --> 00:04:08.200
 n or prevents DNS lookup

75
00:04:09.500 --> 00:04:12.700
choose a cute apart scanning. We will get help from service that

76
00:04:12.700 --> 00:04:16.300
 are running in our Linux environment. A service

77
00:04:16.300 --> 00:04:20.100
 is an application that runs in the background waiting

78
00:04:19.100 --> 00:04:22.200
 for someone or something to use

79
00:04:22.200 --> 00:04:22.500
 it.

80
00:04:23.100 --> 00:04:27.000
And Linux in Microsoft Windows has a lot of services press

81
00:04:26.000 --> 00:04:27.300
 started.

82
00:04:28.100 --> 00:04:32.400
Come for example SSH or in Apache

83
00:04:31.400 --> 00:04:34.700
 2 web server in our

84
00:04:34.700 --> 00:04:38.300
 example here. We're going to use the Apache HTTP

85
00:04:37.300 --> 00:04:38.900
 server.

86
00:04:39.900 --> 00:04:42.700
First we will get its status.

87
00:04:47.800 --> 00:04:51.100
So we are starting check the

88
00:04:50.100 --> 00:04:53.500
 status of the apesh HTTP server.

89
00:04:54.600 --> 00:04:57.900
So we get this this comment.

90
00:05:10.300 --> 00:05:13.000
And this moment the service is not

91
00:05:13.000 --> 00:05:13.300
 running.

92
00:05:15.100 --> 00:05:16.300
So we will start.

93
00:05:19.500 --> 00:05:24.800
And check

94
00:05:23.800 --> 00:05:26.400
 his status again.

95
00:05:34.400 --> 00:05:38.400
Okay, now the status of active that's

96
00:05:38.400 --> 00:05:39.800
 mean that the server is running.

97
00:05:42.800 --> 00:05:44.000
and in the another

98
00:05:45.300 --> 00:05:48.600
Terminal here. We will start a pot

99
00:05:48.600 --> 00:05:50.600
 scanning. So you start a net get

100
00:05:51.200 --> 00:05:54.900
in a client mode to try to connect

101
00:05:54.900 --> 00:05:57.800
 or try to verify if the if

102
00:05:57.800 --> 00:06:00.600
 a specific Port is running or

103
00:06:00.600 --> 00:06:02.200
 is is open actually.

104
00:06:04.200 --> 00:06:04.800
So let's

105
00:06:05.700 --> 00:06:08.700
next let's see is

106
00:06:18.300 --> 00:06:20.600
so new in this in this terminal here.

107
00:06:21.400 --> 00:06:23.700
restart our netcat We Run The netcat

108
00:06:24.300 --> 00:06:27.500
In localhost, that's mean the same machine

109
00:06:27.500 --> 00:06:30.400
 that we are working here and in a specific

110
00:06:30.400 --> 00:06:31.900
 Port 80.

111
00:06:32.400 --> 00:06:34.600
in the result of netcat was the

112
00:06:36.100 --> 00:06:38.900
this port is open, which is open.

113
00:06:42.400 --> 00:06:43.000
We can use.

114
00:06:43.900 --> 00:06:47.300
Another combination of options are

115
00:06:46.300 --> 00:06:51.000
 available in available in netcat to make

116
00:06:49.300 --> 00:06:52.500
 a port scanning.

117
00:06:53.100 --> 00:06:56.100
And using a range of ports.

118
00:07:08.300 --> 00:07:12.200
So this is an example here. We are using our double v

119
00:07:11.200 --> 00:07:14.300
 option. That's mean that we we're going more

120
00:07:14.300 --> 00:07:18.100
 details about any step that netcat is

121
00:07:18.100 --> 00:07:19.300
 is operating.

122
00:07:20.400 --> 00:07:23.500
We are using a dash. I

123
00:07:23.500 --> 00:07:27.400
 let's mean that we are setting a delay

124
00:07:27.400 --> 00:07:29.700
 interval between the scanning for each port.

125
00:07:30.700 --> 00:07:33.400
And we are using to option Z

126
00:07:33.200 --> 00:07:36.700
 - Z for the status for

127
00:07:36.700 --> 00:07:38.200
 a for each door.

128
00:07:39.100 --> 00:07:42.700
And for our range we are using we are

129
00:07:42.700 --> 00:07:43.100
 going

130
00:07:44.100 --> 00:07:45.700
the beginning is to

131
00:07:46.900 --> 00:07:48.700
the minimum value of the port

132
00:07:49.800 --> 00:07:52.800
the like the minimal index and the

133
00:07:52.800 --> 00:07:56.300
 the final Port the

134
00:07:55.300 --> 00:07:58.200
 high option is the

135
00:07:58.200 --> 00:08:01.200
 the high part that's mean

136
00:08:01.200 --> 00:08:05.100
 that they our range our range of ports. You

137
00:08:04.100 --> 00:08:08.700
 start going for the the downpours and

138
00:08:08.700 --> 00:08:10.100
 going to the airport.

139
00:08:15.300 --> 00:08:18.600
So the operation here is the dead cat

140
00:08:18.600 --> 00:08:22.100
 will run this range and we

141
00:08:21.100 --> 00:08:24.400
 will review return our

142
00:08:24.400 --> 00:08:25.500
 result for each port.

143
00:08:28.200 --> 00:08:31.100
in the in the the range so

144
00:08:32.300 --> 00:08:35.400
Now we can see that some ports are refused. That means

145
00:08:35.400 --> 00:08:38.300
 that it's open. There are closed and some

146
00:08:38.300 --> 00:08:41.300
 parts are open. So the server here is

147
00:08:41.300 --> 00:08:41.700
 open.

148
00:08:44.100 --> 00:08:47.600
If we will try another thing is to stop the

149
00:08:47.600 --> 00:08:50.800
 service and run again, the the parts

150
00:08:50.800 --> 00:08:51.100
 scanning.

151
00:08:51.900 --> 00:08:55.400
So you use this service here?

152
00:09:03.400 --> 00:09:07.000
Okay, so that's mean that the service of up Apache to

153
00:09:06.400 --> 00:09:08.000
 is stop.

154
00:09:15.100 --> 00:09:19.400
They status prove the the common stop.

155
00:09:19.400 --> 00:09:21.400
 So the service is not available anymore.

156
00:09:22.500 --> 00:09:22.700
and

157
00:09:24.400 --> 00:09:27.600
we'll check again if the door the open the

158
00:09:27.600 --> 00:09:28.000
 door is open.

159
00:09:28.800 --> 00:09:30.000
So the door is refusing.

160
00:09:30.600 --> 00:09:33.200
Let's mean the netcat is able to verify a specific

161
00:09:33.200 --> 00:09:35.300
 port or a port range.

162
00:09:35.900 --> 00:09:38.500
to check the head surface

163
00:09:45.100 --> 00:09:48.300
For transferring file sample, we will start by creating

164
00:09:48.300 --> 00:09:50.800
 a cutting her face to produce a file.

165
00:09:51.700 --> 00:09:54.900
And use it in this example like before

166
00:09:54.900 --> 00:09:57.800
 let's start a shot interface, but

167
00:09:57.800 --> 00:10:00.700
 now we need a little difference. We we will

168
00:10:00.700 --> 00:10:03.400
 log all the text Exchange in a log file

169
00:10:03.400 --> 00:10:04.800
 when the command

170
00:10:11.300 --> 00:10:11.500
so

171
00:10:12.900 --> 00:10:15.400
this we are creating Isis of netcat

172
00:10:15.400 --> 00:10:18.700
 in a seven mode, but deliver difference is

173
00:10:18.700 --> 00:10:20.800
 that we are passing the option.

174
00:10:22.300 --> 00:10:23.200
Dash oh

175
00:10:24.400 --> 00:10:27.600
and we will specify a name of a file

176
00:10:27.600 --> 00:10:31.100
 to reach to log all the the text

177
00:10:30.100 --> 00:10:32.200
 Exchange.

178
00:10:33.300 --> 00:10:34.500
in this communication

179
00:10:38.200 --> 00:10:41.700
and for our example here, we will use a

180
00:10:41.700 --> 00:10:43.300
 damp got X fire.

181
00:10:43.900 --> 00:10:44.100
Okay.

182
00:10:46.400 --> 00:10:50.200
And now the server is ready to to connect

183
00:10:49.200 --> 00:10:52.500
 with any to any server

184
00:10:52.500 --> 00:10:55.200
 in the side in the client mode.

185
00:10:56.400 --> 00:10:59.600
In the client side, we start a

186
00:10:59.600 --> 00:11:02.900
 sense of netcat and connecting. I mean

187
00:11:02.900 --> 00:11:03.300
 this server.

188
00:11:04.900 --> 00:11:06.500
in a port 1 2 3 4 5

189
00:11:12.700 --> 00:11:15.600
Okay. So now we have the the connection and let's

190
00:11:15.600 --> 00:11:19.000
 start to exchange some text.

191
00:11:34.300 --> 00:11:37.600
Okay, so we finished the connection.

192
00:11:38.500 --> 00:11:41.400
The file it's here. The

193
00:11:41.400 --> 00:11:42.800
 file is is created.

194
00:11:43.400 --> 00:11:46.000
And let's let take a look of the

195
00:11:46.500 --> 00:11:49.400
 content of this file using the option kit

196
00:11:49.400 --> 00:11:53.200
 to get the information. So the

197
00:11:52.200 --> 00:11:53.600
 information here.

198
00:11:54.700 --> 00:11:57.800
We have in the left side. We have extra decimal

199
00:11:57.800 --> 00:12:01.300
 for every character Exchange in

200
00:12:01.300 --> 00:12:02.600
 the in the communication.

201
00:12:03.800 --> 00:12:06.800
So in the left, we have the the X information

202
00:12:06.800 --> 00:12:09.100
 xlax information in the in the right.

203
00:12:09.100 --> 00:12:12.500
 We have the text information. So we log

204
00:12:12.500 --> 00:12:14.300
 all the conversation here.

205
00:12:15.900 --> 00:12:19.400
Okay, so now let's run

206
00:12:18.400 --> 00:12:21.000
 again. Netcat.

207
00:12:21.800 --> 00:12:24.300
And we will pass.

208
00:12:25.500 --> 00:12:26.500
this file

209
00:12:27.200 --> 00:12:30.600
to this from the server to the client. So let's

210
00:12:30.600 --> 00:12:31.000
 start.

211
00:12:33.100 --> 00:12:34.900
Sorry mode not get so.

212
00:12:39.100 --> 00:12:41.700
So the difference here is that we are passing.

213
00:12:43.900 --> 00:12:46.900
The file to the connection the

214
00:12:46.900 --> 00:12:49.600
 common here means that we

215
00:12:49.600 --> 00:12:52.900
 are creating server mode. Let

216
00:12:52.900 --> 00:12:55.600
 net get and now we are passing the

217
00:12:55.600 --> 00:12:56.000
 file.

218
00:12:56.900 --> 00:12:59.800
To the client who who connects

219
00:12:59.800 --> 00:13:02.900
 the server we receive this file

220
00:13:02.900 --> 00:13:04.500
 as as a result.

221
00:13:06.400 --> 00:13:10.500
And in the client mode, we are creating an

222
00:13:09.500 --> 00:13:12.800
 instance of Netcare in

223
00:13:12.800 --> 00:13:13.200
 this common here.

224
00:13:21.500 --> 00:13:25.400
Okay, so we are using the W number two,

225
00:13:25.400 --> 00:13:28.400
 that's me that we are setting a timeout for the

226
00:13:28.400 --> 00:13:29.700
 communication.

227
00:13:30.600 --> 00:13:33.800
and as a result of this

228
00:13:33.800 --> 00:13:36.300
 of this call a communication of

229
00:13:36.300 --> 00:13:39.600
 Disconnect, we are creating a new file so

230
00:13:39.600 --> 00:13:40.500
 we have to specify

231
00:13:41.800 --> 00:13:43.600
the name of this new file

232
00:13:49.600 --> 00:13:52.600
like this, so this comment means

233
00:13:52.600 --> 00:13:52.800
 that

234
00:13:54.200 --> 00:13:57.000
the connection when when the connection is done.

235
00:13:57.700 --> 00:14:00.500
The the content the object

236
00:14:00.500 --> 00:14:03.400
 the content that that we are receiving way that

237
00:14:03.400 --> 00:14:06.800
 we are receiving we will put in this

238
00:14:06.800 --> 00:14:08.200
 new fire here.

239
00:14:09.700 --> 00:14:14.000
Okay, so let me start the server this

240
00:14:12.600 --> 00:14:15.000
 and let me

241
00:14:15.300 --> 00:14:16.300
 start the client.

242
00:14:18.200 --> 00:14:20.900
So the connection is done. It's okay.

243
00:14:22.200 --> 00:14:23.900
Let me interrupt the

244
00:14:25.200 --> 00:14:28.400
the connection and let me list the files

245
00:14:28.400 --> 00:14:31.800
 so we have the copy.

246
00:14:32.900 --> 00:14:35.400
X file here. So let take a

247
00:14:35.400 --> 00:14:36.900
 look of his content.

248
00:14:38.500 --> 00:14:39.600
with a common cat

249
00:14:44.100 --> 00:14:47.200
and the content is the same. So that's mean that the file

250
00:14:47.200 --> 00:14:50.500
 was transferred from one point to

251
00:14:50.500 --> 00:14:53.400
 another Point another another.

252
00:14:54.700 --> 00:14:58.100
Another check that we can see that you

253
00:14:57.100 --> 00:15:00.500
 can use for to verify if the file

254
00:15:00.500 --> 00:15:01.900
 is the the original file.

255
00:15:02.800 --> 00:15:05.200
We can use a command line.

256
00:15:06.400 --> 00:15:09.300
Md5 sun to check the hash of the file.

257
00:15:10.100 --> 00:15:14.300
This means these two will compute compute and

258
00:15:14.300 --> 00:15:17.200
 check the md5 hash file. This is

259
00:15:17.200 --> 00:15:20.300
 a 128 beat Jackson and we

260
00:15:20.300 --> 00:15:23.500
 use it to verify the Integrity of

261
00:15:23.500 --> 00:15:24.200
 the file.

262
00:15:24.800 --> 00:15:27.900
So in this property here, we are

263
00:15:27.900 --> 00:15:30.800
 using the command md5 Sun.

264
00:15:32.100 --> 00:15:34.600
and the name of the file dump

265
00:15:35.600 --> 00:15:38.900
what act so we have the in the

266
00:15:38.900 --> 00:15:42.700
 left the hash the hash information?

267
00:15:43.900 --> 00:15:46.300
And in the right the name of the

268
00:15:46.300 --> 00:15:46.500
 file.

269
00:15:48.200 --> 00:15:51.400
And we will do the same for the new the new fire that we

270
00:15:51.400 --> 00:15:52.400
 we created.

271
00:15:55.400 --> 00:15:56.700
md5 Sun

272
00:16:00.500 --> 00:16:04.200
copy X and we can check the the hash of

273
00:16:03.200 --> 00:16:06.500
 the both side files are

274
00:16:06.500 --> 00:16:09.800
 the same. So that means that the is the

275
00:16:09.800 --> 00:16:12.600
 same file the Integrity is okay

276
00:16:12.600 --> 00:16:15.300
 and our example here for the

277
00:16:15.300 --> 00:16:16.700
 exchange of the file.

278
00:16:17.800 --> 00:16:18.500
It's okay.

279
00:16:25.500 --> 00:16:28.800
Bonnie grabbing it's enumeration technique, which

280
00:16:28.800 --> 00:16:32.200
 is designed to determine the brain version

281
00:16:31.200 --> 00:16:34.900
 operating system or other

282
00:16:34.900 --> 00:16:37.600
 relevant information about a particular

283
00:16:37.600 --> 00:16:39.300
 service or application.

284
00:16:40.400 --> 00:16:43.900
The idea here is to look if there is any vulnerability

285
00:16:43.900 --> 00:16:46.400
 associated with a particular version

286
00:16:46.400 --> 00:16:49.900
 of some Services system or component.

287
00:16:50.800 --> 00:16:53.800
In our example, we are running netcat on

288
00:16:53.800 --> 00:16:56.900
 client mode and we are looking for a SSH

289
00:16:56.900 --> 00:16:59.400
 service running in the

290
00:16:59.400 --> 00:17:00.100
 port 22.

291
00:17:00.800 --> 00:17:05.000
In this example, it's possible to check the ip+port

292
00:17:03.600 --> 00:17:06.900
 when kind of services running

293
00:17:06.900 --> 00:17:09.500
 in this Sport and

294
00:17:09.500 --> 00:17:11.100
 which version of this service?

295
00:17:12.200 --> 00:17:12.700
So let's start.

296
00:17:13.700 --> 00:17:16.300
In check if the S is

297
00:17:16.300 --> 00:17:20.300
 SSH service is running or

298
00:17:19.300 --> 00:17:20.500
 not.

299
00:17:21.200 --> 00:17:22.600
So we are using the common.

300
00:17:27.600 --> 00:17:28.100
so

301
00:17:28.900 --> 00:17:31.600
Service SSH status to

302
00:17:31.600 --> 00:17:34.200
 get the information if there is

303
00:17:34.200 --> 00:17:37.200
 the service is always running or not.

304
00:17:37.200 --> 00:17:40.500
 So the service for the SSH is

305
00:17:40.500 --> 00:17:41.400
 not running.

306
00:17:42.300 --> 00:17:45.200
So it's okay. So let's start this service.

307
00:17:46.200 --> 00:17:47.000
when the common

308
00:17:51.300 --> 00:17:51.700
start

309
00:17:54.100 --> 00:17:58.500
and check again if this service is running now

310
00:17:58.500 --> 00:17:59.200
 or not.

311
00:18:03.500 --> 00:18:07.200
Great. So the service is running and this

312
00:18:06.200 --> 00:18:09.900
 okay for continuity test.

313
00:18:10.600 --> 00:18:14.300
So let's start the sh SSH.

314
00:18:20.400 --> 00:18:23.900
So we are starting the subsid the protocol here.

315
00:18:29.600 --> 00:18:32.400
It's okay. The the program is it's

316
00:18:32.400 --> 00:18:32.800
 running.

317
00:18:33.700 --> 00:18:36.700
And let in the other in India

318
00:18:36.700 --> 00:18:38.500
 and other terminal let's check.

319
00:18:39.400 --> 00:18:42.500
The situation of these of this port so

320
00:18:42.500 --> 00:18:45.400
 let's start a netcat in the

321
00:18:45.400 --> 00:18:45.800
 client mode.

322
00:18:53.100 --> 00:18:57.200
So now we can check that the port 22

323
00:18:56.200 --> 00:18:59.600
 is open and which service

324
00:18:59.600 --> 00:19:02.300
 is associated with this services.

325
00:19:03.300 --> 00:19:04.300
Is SSH?

326
00:19:05.700 --> 00:19:08.700
And we can verify which version

327
00:19:08.700 --> 00:19:11.400
 of open SSH is running.

328
00:19:12.100 --> 00:19:16.500
So all this is all this information is very interesting interesting

329
00:19:15.500 --> 00:19:18.800
 to get into aim

330
00:19:18.800 --> 00:19:21.400
 to search if there is any vulnerability.

331
00:19:22.100 --> 00:19:26.900
Associated with this combination of board the

332
00:19:25.900 --> 00:19:29.100
 services and the

333
00:19:28.100 --> 00:19:31.300
 the version of service that

334
00:19:31.300 --> 00:19:31.900
 is running.

335
00:19:39.500 --> 00:19:41.700
redirecting ports and traffic

336
00:19:42.900 --> 00:19:45.300
using netcat for redirect reports and

337
00:19:45.300 --> 00:19:48.700
 traffic is an option available to simulate and

338
00:19:48.700 --> 00:19:51.700
 attack call it a middleman attack

339
00:19:51.700 --> 00:19:54.100
 when they attack appears to

340
00:19:54.100 --> 00:19:55.600
 be coming from one node.

341
00:19:56.300 --> 00:19:58.600
But the original node is another one.

342
00:19:59.400 --> 00:20:01.700
Multiple had directs can be done.

343
00:20:02.500 --> 00:20:05.700
One popular name for this kind of redirection of traffic

344
00:20:05.700 --> 00:20:07.600
 is called a relay.

345
00:20:08.500 --> 00:20:12.000
So in this example here we are using three different

346
00:20:11.000 --> 00:20:13.300
 terminals.

347
00:20:14.700 --> 00:20:18.300
And we are using a Linux environment and Microsoft

348
00:20:17.300 --> 00:20:19.400
 Windows environment.

349
00:20:20.200 --> 00:20:23.500
And we are using three different kind of terminal. So

350
00:20:23.500 --> 00:20:27.400
 we call it Terminal 3 here Terminal 2

351
00:20:27.400 --> 00:20:30.600
 here and Terminal 1 here.

352
00:20:32.900 --> 00:20:33.100
So

353
00:20:34.300 --> 00:20:35.300
in the terminal 3

354
00:20:36.500 --> 00:20:40.400
We are simulating a connection. So

355
00:20:39.400 --> 00:20:42.700
 let's start server mode

356
00:20:42.700 --> 00:20:44.800
 here and that get several mode.

357
00:20:45.700 --> 00:20:46.600
using the option

358
00:20:55.700 --> 00:20:58.700
So in the terminal 3 we are using we

359
00:20:58.700 --> 00:21:02.000
 are running access of that cat in server

360
00:21:01.000 --> 00:21:02.200
 mode.

361
00:21:02.800 --> 00:21:05.500
And we will listen the part 5.

362
00:21:06.500 --> 00:21:07.900
4321

363
00:21:09.600 --> 00:21:10.500
in Terminal 2

364
00:21:12.800 --> 00:21:16.400
We will again running

365
00:21:15.400 --> 00:21:18.700
 a netcat in

366
00:21:18.700 --> 00:21:19.500
 the server mode.

367
00:21:20.700 --> 00:21:22.400
but when a little different

368
00:21:23.400 --> 00:21:23.700
here

369
00:21:28.800 --> 00:21:31.600
so at this moment, I'm running not getting

370
00:21:31.600 --> 00:21:34.400
 sense in server mode and listen for

371
00:21:34.400 --> 00:21:37.400
 listen to another Port one, two, three,

372
00:21:37.400 --> 00:21:37.800
 four five.

373
00:21:38.600 --> 00:21:38.900
Okay.

374
00:21:40.300 --> 00:21:42.800
and the result of this connection

375
00:21:44.600 --> 00:21:47.200
I will use the pipe operator here.

376
00:21:47.800 --> 00:21:50.200
That's mean that there is the result of

377
00:21:50.200 --> 00:21:52.600
 this connection will be I put

378
00:21:53.400 --> 00:21:56.200
to another command and this common is a

379
00:21:56.200 --> 00:21:59.900
 is a common is a netcat running

380
00:21:59.900 --> 00:22:02.900
 in a client mode connecting to

381
00:22:02.900 --> 00:22:04.000
 the terminal 3.

382
00:22:14.500 --> 00:22:16.100
Okay, so the Terminal 2.

383
00:22:17.600 --> 00:22:21.500
I have I I run a netcat in

384
00:22:21.500 --> 00:22:24.300
 a server mode and the input of

385
00:22:24.300 --> 00:22:27.200
 this connection will be the result of

386
00:22:27.200 --> 00:22:31.600
 this connection will be I put to another instance

387
00:22:30.600 --> 00:22:34.300
 of netcat, but when

388
00:22:33.300 --> 00:22:36.200
 a connection to a terminal 3

389
00:22:37.100 --> 00:22:40.000
Okay, and in the terminal 1 here?

390
00:22:41.100 --> 00:22:44.100
So I'm I'm running as I said,

391
00:22:44.100 --> 00:22:47.200
 I'm running a Linux environment and our Windows environment.

392
00:22:48.100 --> 00:22:51.500
They are in the same. They are different machines, but

393
00:22:51.500 --> 00:22:53.900
 they are in the same network.

394
00:22:54.900 --> 00:22:57.600
In the terminal one here will be

395
00:22:57.600 --> 00:23:00.800
 my my first

396
00:23:00.800 --> 00:23:03.500
 my start point of

397
00:23:03.500 --> 00:23:04.100
 command.

398
00:23:04.900 --> 00:23:07.700
For this and links between

399
00:23:07.700 --> 00:23:10.700
 notes between netcat instance. So

400
00:23:13.100 --> 00:23:13.400
will be

401
00:23:16.300 --> 00:23:17.200
a netcat

402
00:23:18.500 --> 00:23:22.000
now is a kind of fresh off netcat. So I will use

403
00:23:21.300 --> 00:23:24.200
 the IP of these machine here

404
00:23:24.200 --> 00:23:25.700
 running Linux.

405
00:23:26.700 --> 00:23:27.300
So we'll be.

406
00:23:34.400 --> 00:23:37.700
Like this, this is my IP for the

407
00:23:37.700 --> 00:23:40.400
 machine running my Linux environment

408
00:23:40.400 --> 00:23:40.600
 here.

409
00:23:41.500 --> 00:23:44.400
And now I'll use a port this

410
00:23:44.400 --> 00:23:47.300
 port you want to for five. So that's mean

411
00:23:47.300 --> 00:23:51.200
 that the the net get here is the

412
00:23:51.200 --> 00:23:54.800
 distance running in my Microsoft Windows here.

413
00:23:56.500 --> 00:23:56.600
We'll connect.

414
00:23:57.600 --> 00:23:59.900
this netcat here in Terminal 2

415
00:24:00.700 --> 00:24:02.900
in the Linux environment

416
00:24:06.100 --> 00:24:06.900
in the port

417
00:24:12.300 --> 00:24:16.000
so that's mean that now I have a connection from Terminal

418
00:24:15.200 --> 00:24:19.400
 1 to Terminal 2 and a

419
00:24:18.400 --> 00:24:22.300
 redirecting to another

420
00:24:23.700 --> 00:24:27.100
terminal Terminal 3 in another instance

421
00:24:26.100 --> 00:24:28.600
 of netcat here

422
00:24:29.600 --> 00:24:32.400
so at this moment if I type type a

423
00:24:32.400 --> 00:24:35.400
 messenger from this terminal here like

424
00:24:39.800 --> 00:24:42.800
In Terminal 1 the terminal 3. We

425
00:24:42.800 --> 00:24:45.100
 receive this command that means

426
00:24:45.100 --> 00:24:47.900
 that the term the the information here.

427
00:24:49.200 --> 00:24:50.900
in the terminal 1

428
00:24:52.200 --> 00:24:55.400
press through the terminal 2 and

429
00:24:56.500 --> 00:24:59.400
arrived the terminal 3. So these are

430
00:24:59.400 --> 00:25:03.400
 example of Resurrection head

431
00:25:02.400 --> 00:25:05.800
 directing port and Resurrection traffic.

432
00:25:07.400 --> 00:25:08.100
in this video

433
00:25:08.900 --> 00:25:11.600
we saw different operations with netcat

434
00:25:11.600 --> 00:25:14.600
 and we did some combinations to understand more

435
00:25:14.600 --> 00:25:17.700
 about the possibilities that we can do with this

436
00:25:17.700 --> 00:25:18.400
 fantastic to

437
00:25:20.400 --> 00:25:23.600
In the next session, we will take a look at the basic

438
00:25:23.600 --> 00:25:26.500
 Network fundamentals. That is so important

439
00:25:26.500 --> 00:25:29.900
 for cyber security and penetration testing.
