WEBVTT 00:00.180 --> 00:07.410 There are a ton of port numbers and applications on the exams so what I'm going to do in this episode 00:07.410 --> 00:12.270 is just do a really quick rundown in particular a quick overview of the protocols that you're going 00:12.270 --> 00:13.700 to be seen on the exam. 00:13.770 --> 00:18.540 Port numbers and basic functionality this is going to be really really quick and we're going to be running 00:18.540 --> 00:21.060 through all kinds of them so watch fast. 00:21.060 --> 00:27.000 First is Hypertext Transfer Protocol or Google HTP using TZP port 80. 00:27.000 --> 00:29.240 This is for unsecure Web sites. 00:29.280 --> 00:34.320 Now we always say port 80 for each TTP but you could also see a lot of systems that use default ports 00:34.320 --> 00:37.070 like for example 1880 or something like that. 00:37.080 --> 00:40.210 But the actual default is always 80. 00:40.590 --> 00:47.980 Next is secure a TTP or HTP as this is going to be using TZP port 1:43. 00:48.510 --> 00:54.510 OK now let's talk about remote shells so the first one is going to be ancient old telnet telnet has 00:54.510 --> 01:00.360 been around forever and it uses TCAP port 23 it is completely insecure if you're going to be using a 01:00.360 --> 01:06.240 remote shell today you're going to be using secure shell or S-sh and that's on port 22 in fact. 01:06.240 --> 01:12.990 We're going to see a lot more of S-sh because not only does it make a good shell it can also do tunneling 01:13.020 --> 01:14.700 and other programs can run inside. 01:14.710 --> 01:21.030 So what I want to talk about now is file transfer if we want to move a file from one computer to the 01:21.030 --> 01:23.230 next we've got a lot of protocols in here. 01:23.310 --> 01:27.340 The granddaddy of all is file transfer protocol or FTB. 01:27.420 --> 01:32.910 It uses ports 20 and 21 although in some cases it will only use port 21. 01:32.910 --> 01:35.160 The problem with FGP is it's completely insecure. 01:35.160 --> 01:38.270 So there's a bunch of alternatives to regular FTB. 01:38.370 --> 01:41.260 The first one is FGP over S-sh. 01:41.280 --> 01:46.890 So basically we set up an S-sh connection instead of just using it as a remote shell. 01:46.890 --> 01:49.740 We fire up an FPP program and run it through it. 01:49.740 --> 01:55.290 So if we were doing FCP over S-sh we're using port 22. 01:55.350 --> 01:57.330 Another option is FGP. 01:57.330 --> 01:57.870 Yes. 01:57.960 --> 02:04.530 Basically what they did is they took old FGP and they added the same SSL T.L. security that we have 02:04.530 --> 02:05.360 with HTP. 02:05.360 --> 02:06.220 Yes. 02:06.270 --> 02:13.960 So it runs on FCP ports 20 and 21 just like regular FTB However it's completely secure. 02:14.730 --> 02:17.110 Next is s FGP. 02:17.220 --> 02:23.100 This is called S-sh file transfer protocol or secure firewall transfer protocol. 02:23.100 --> 02:28.080 This sounds the same but it's a totally different protocol that FCP and has really great security and 02:28.080 --> 02:29.840 it runs on port 22. 02:31.020 --> 02:34.820 Next is called secure copy or SEP. 02:34.830 --> 02:38.190 This is a very primitive file transfer over S-sh. 02:38.250 --> 02:40.750 It's just a command line now with these other FGP. 02:40.770 --> 02:44.020 You could actually make folders on the remote system and stuff like that. 02:44.040 --> 02:47.340 This thing only moves files it's very primitive but it still works. 02:48.560 --> 02:58.610 Next is trivial FTB TFT P is exactly as it sounds a very trivial form of FGP it only allows you to copy 02:58.610 --> 03:05.650 files and it runs on UDP it's one of the very few protocols that runs on UDP and that's UDP port 69. 03:06.170 --> 03:11.730 Now Windows systems also move a lot of files sharing folders and that type of stuff. 03:11.810 --> 03:16.770 It doesn't use any of these FGP it's got its own Microsoft NET biased protocol. 03:16.790 --> 03:21.540 So net bias originally ran on Portes 1:37 1:38 1:39. 03:21.560 --> 03:26.840 However the more modern versions use something called SMB server message block and that runs on port 03:26.840 --> 03:28.660 445. 03:29.030 --> 03:30.960 Next let's talk about mail. 03:31.100 --> 03:36.500 If you're sending mail you're going to be using the simple mail transfer protocol S-M T.P. it runs on 03:36.500 --> 03:37.970 TCAP port 25. 03:37.960 --> 03:41.750 And remember that sends our mail to the other folks. 03:41.930 --> 03:47.150 Now to get your mail back you have a choice you can either use IMAP or you can use POP IMAP stands for 03:47.210 --> 03:51.080 Internet message Access Protocol it uses port 1:43. 03:51.170 --> 03:56.350 Pop is an older protocol but still quite popular and it uses port 110. 03:56.390 --> 03:59.380 OK let's move into the world of what I'm just going to call eccentric. 03:59.390 --> 04:00.710 These these are all over the place. 04:00.860 --> 04:03.750 Number one the famous DNS domain name system. 04:03.860 --> 04:09.510 This is what allows us to use names like W WW that total CENTCOM and things like that. 04:09.560 --> 04:17.550 It runs on TCAP port 53 next is DHC C.P. or Dynamic Host Configuration Protocol. 04:17.730 --> 04:22.940 DHC is all it allows us to have dynamic IP addresses instead of having to type in IP addresses and all 04:22.940 --> 04:23.870 our computers. 04:24.060 --> 04:33.250 It's going to use UDP port 67 and 68 next is simple network management protocol and overall protocol 04:33.250 --> 04:39.750 we use for organizing our networks we can have as an MP have our routers talk to us and stuff like that. 04:39.790 --> 04:51.750 It uses UDP ports 161 and 162 Elda app or lightweight directory access protocol uses port 389 last for 04:51.840 --> 04:52.920 remote desktops. 04:52.920 --> 04:59.130 This is used heavily by Windows for example is RTP RTP protocol which is the underpinning which allows 04:59.130 --> 05:05.680 us to log into remote desktops uses TCAP port 33 89. 05:05.990 --> 05:11.570 Now folks you're going to be seeing more of all of these protocols in different episodes so what I'm 05:11.630 --> 05:17.450 only trying to do here is give you a nice organized pile so that you make sure you're comfortable with 05:17.450 --> 05:21.800 a whole bunch of port numbers and a whole bunch of functionalities with a whole bunch of protocols.