Now there are a system is installed and we have a validated network connectivity let's ensure our system
has the latest and greatest software packages and updates to do that.
We will use the advanced package tool called apt to update the operating system and tools on our Kelly
system.
What configure our system to use bleeding edge tools and updates and also discuss the risks associated
with doing so.
And we will also pin certain software packages to stay at a specific version and not get upgraded which
is handy if you run into one or more packages that have compatibility or dependency issues.
The first thing we need to do is update our systems so that it knows about the newest versions of packages
and their dependencies.
To do that we will issue the apt tech get space update command.
For those of you who are more comfortable with Windows systems I equate this command to asking your
system to check for updates without actually pulling the trigger and installing them when that completes
and we're ready to actually newest versions of packed.
We can issue the apt tech get space upgrade command.
Now you'll notice that before our system starts the update process it asks us to confirm the operation
so we can just hit Y and then hit enter to continue.
However for now I'm going to hit control plus C to cancel out of this for now to show you another way
to apply updates without getting prompted for that extra confirmation.
As we learned in the last module we can use the up and down arrows to access commands we've previously
typed in the terminal.
So I'm going to hit the up arrow a few times and then I'm going to add a space.
Y to my last command.
And what this tack.
Why does is it automatically answer is yes.
On our behalf without stopping for a prompt.
So you'll see.
Now if I hit enter the updates start installing automatically.
Just to show a little behind the scenes look at how apt is configured.
Let's open up the slash at see slash apt slash sources list file the highlighted line shows that we
are using the Kalli rolling release.
Now typically a rolling release is a Linux distribution that is constantly being updated with the latest
patches and features.
And for the most part I'd recommend leaving this sources out list file completely alone as the standard
Cauley patches and features should be sufficient for most users.
However there may be a time where you need to work with versions of tools that are in a beta or experimental
phase and not quite ready for general public use.
Kelly refers to this as their bleeding edge repository and it can be enabled by typing the commands
you see me putting in my terminal window.
So now that we've added the bleeding edge repository Let's do another apt get update cycle so that our
system knows about the new packages that are now available from here.
We can select one or more packages to install from the bleeding edge repository for example if I wanted
to install the bleeding edge version of sequel map I would type apt space install space sequel map slash
Kalli tech bleeding tech edge and hit enter and now if we run the sequel map command we can see we're
running version 1.
1 10 9.
If for some reason we've made a mistake and want to go back to the standard Kalli ruling version that's
no problem.
Just type the same command but this time specified the Kalli rolling repository.
And if we run sequel map one more time we can see we are back to the 1 1 11 stable version.
The last thing I want to show you in this module is how to pin certain software packages to your system
so that they don't get updated.
When we run the apt get update and apt get upgrade cycle.
So first let's go back in time when we had just run the apt get update and were ready to install a bunch
of updated packages on our machine.
Before we execute the apt get upgrade to actually do that.
Let's run a command called apt space.
List space tech tech upgradable.
What this will do is list all the packages that will be updated by the upgrade process.
As you can see several screens worth of tools whipped by us pretty fast so let's run that command one
more time but add the pipe symbol and then the word more and hit enter.
What this does is forces our output to scroll by a page at a time and we can simply advance to the next
screen when we're ready by pressing the spacebar
one of the packages that is going to be updated in this cycle is zed attack proxy and its package name
is Z proxy.
It will be updated from a 2.6 version to a 2.7 version.
We can confirm that by issuing the apt get upgrade command and there is zero a proxy in the list.
Now let's say that for some reason I know that my machine doesn't work with the 2.7 version and therefore
I never want it to be upgraded automatically.
What I can do is create a file in slash at c slash apt called preferences and use the following format
which will specify that I want z a proxy to stay locked in at a 2.6 version and never automatically
get upgraded to a 2.7 version.
To confirm this worked let's do another round of apt get update and apt get upgrade and this time we
should see that ZA proxy is missing from our list of packages because we have specified we wanted to
stay locked in at the 2.6 version and never get updated automatically in our next video.
We will create a non-root user on our Kelly system which will help keep us from making drastic system
changes without thinking them through and in general make our day to day use of Kalli more secure.