WEBVTT

00:01.530 --> 00:07.650
Now there are a system is installed and we have a validated network connectivity let's ensure our system

00:07.650 --> 00:12.760
has the latest and greatest software packages and updates to do that.

00:12.780 --> 00:20.430
We will use the advanced package tool called apt to update the operating system and tools on our Kelly

00:20.430 --> 00:21.200
system.

00:22.210 --> 00:28.270
What configure our system to use bleeding edge tools and updates and also discuss the risks associated

00:28.270 --> 00:29.250
with doing so.

00:30.260 --> 00:37.310
And we will also pin certain software packages to stay at a specific version and not get upgraded which

00:37.310 --> 00:42.980
is handy if you run into one or more packages that have compatibility or dependency issues.

00:43.700 --> 00:49.760
The first thing we need to do is update our systems so that it knows about the newest versions of packages

00:49.850 --> 00:51.370
and their dependencies.

00:52.130 --> 00:58.060
To do that we will issue the apt tech get space update command.

00:58.170 --> 01:03.330
For those of you who are more comfortable with Windows systems I equate this command to asking your

01:03.330 --> 01:11.380
system to check for updates without actually pulling the trigger and installing them when that completes

01:11.380 --> 01:14.520
and we're ready to actually newest versions of packed.

01:14.740 --> 01:21.590
We can issue the apt tech get space upgrade command.

01:21.600 --> 01:27.600
Now you'll notice that before our system starts the update process it asks us to confirm the operation

01:28.500 --> 01:33.090
so we can just hit Y and then hit enter to continue.

01:33.120 --> 01:40.440
However for now I'm going to hit control plus C to cancel out of this for now to show you another way

01:40.440 --> 01:45.560
to apply updates without getting prompted for that extra confirmation.

01:45.710 --> 01:51.650
As we learned in the last module we can use the up and down arrows to access commands we've previously

01:51.650 --> 01:53.130
typed in the terminal.

01:53.300 --> 01:58.940
So I'm going to hit the up arrow a few times and then I'm going to add a space.

01:59.090 --> 02:01.070
Y to my last command.

02:01.400 --> 02:02.650
And what this tack.

02:02.660 --> 02:06.000
Why does is it automatically answer is yes.

02:06.050 --> 02:09.810
On our behalf without stopping for a prompt.

02:09.980 --> 02:10.680
So you'll see.

02:10.680 --> 02:15.420
Now if I hit enter the updates start installing automatically.

02:18.270 --> 02:22.760
Just to show a little behind the scenes look at how apt is configured.

02:22.770 --> 02:31.580
Let's open up the slash at see slash apt slash sources list file the highlighted line shows that we

02:31.580 --> 02:34.310
are using the Kalli rolling release.

02:34.310 --> 02:40.620
Now typically a rolling release is a Linux distribution that is constantly being updated with the latest

02:40.620 --> 02:42.510
patches and features.

02:42.510 --> 02:48.810
And for the most part I'd recommend leaving this sources out list file completely alone as the standard

02:48.810 --> 02:52.760
Cauley patches and features should be sufficient for most users.

02:54.580 --> 03:00.970
However there may be a time where you need to work with versions of tools that are in a beta or experimental

03:00.970 --> 03:05.030
phase and not quite ready for general public use.

03:05.250 --> 03:11.760
Kelly refers to this as their bleeding edge repository and it can be enabled by typing the commands

03:11.760 --> 03:14.120
you see me putting in my terminal window.

03:16.500 --> 03:23.010
So now that we've added the bleeding edge repository Let's do another apt get update cycle so that our

03:23.010 --> 03:28.560
system knows about the new packages that are now available from here.

03:28.580 --> 03:35.410
We can select one or more packages to install from the bleeding edge repository for example if I wanted

03:35.410 --> 03:44.140
to install the bleeding edge version of sequel map I would type apt space install space sequel map slash

03:44.320 --> 03:52.610
Kalli tech bleeding tech edge and hit enter and now if we run the sequel map command we can see we're

03:52.610 --> 03:54.250
running version 1.

03:54.300 --> 03:56.640
1 10 9.

03:58.020 --> 04:02.800
If for some reason we've made a mistake and want to go back to the standard Kalli ruling version that's

04:02.800 --> 04:04.000
no problem.

04:04.000 --> 04:11.060
Just type the same command but this time specified the Kalli rolling repository.

04:11.180 --> 04:19.710
And if we run sequel map one more time we can see we are back to the 1 1 11 stable version.

04:19.730 --> 04:25.640
The last thing I want to show you in this module is how to pin certain software packages to your system

04:25.730 --> 04:27.750
so that they don't get updated.

04:27.770 --> 04:32.330
When we run the apt get update and apt get upgrade cycle.

04:32.330 --> 04:38.720
So first let's go back in time when we had just run the apt get update and were ready to install a bunch

04:38.720 --> 04:40.950
of updated packages on our machine.

04:41.730 --> 04:46.610
Before we execute the apt get upgrade to actually do that.

04:46.680 --> 04:49.500
Let's run a command called apt space.

04:49.600 --> 04:54.950
List space tech tech upgradable.

04:54.990 --> 05:00.560
What this will do is list all the packages that will be updated by the upgrade process.

05:01.620 --> 05:07.080
As you can see several screens worth of tools whipped by us pretty fast so let's run that command one

05:07.080 --> 05:13.740
more time but add the pipe symbol and then the word more and hit enter.

05:13.740 --> 05:21.030
What this does is forces our output to scroll by a page at a time and we can simply advance to the next

05:21.030 --> 05:24.150
screen when we're ready by pressing the spacebar

05:27.110 --> 05:34.300
one of the packages that is going to be updated in this cycle is zed attack proxy and its package name

05:34.300 --> 05:36.570
is Z proxy.

05:36.700 --> 05:43.080
It will be updated from a 2.6 version to a 2.7 version.

05:43.150 --> 05:52.270
We can confirm that by issuing the apt get upgrade command and there is zero a proxy in the list.

05:52.280 --> 05:58.880
Now let's say that for some reason I know that my machine doesn't work with the 2.7 version and therefore

05:58.910 --> 06:02.300
I never want it to be upgraded automatically.

06:02.310 --> 06:12.060
What I can do is create a file in slash at c slash apt called preferences and use the following format

06:12.840 --> 06:21.090
which will specify that I want z a proxy to stay locked in at a 2.6 version and never automatically

06:21.090 --> 06:23.930
get upgraded to a 2.7 version.

06:26.700 --> 06:35.100
To confirm this worked let's do another round of apt get update and apt get upgrade and this time we

06:35.100 --> 06:42.510
should see that ZA proxy is missing from our list of packages because we have specified we wanted to

06:42.510 --> 06:49.680
stay locked in at the 2.6 version and never get updated automatically in our next video.

06:49.680 --> 06:56.190
We will create a non-root user on our Kelly system which will help keep us from making drastic system

06:56.190 --> 07:02.670
changes without thinking them through and in general make our day to day use of Kalli more secure.
