Welcome to part two of this module
in this video.
We're going to start working with recon energy.
Recon energy is an open source intelligence tool similar to multi go that comes prepackaged with Cally
Linux.
Unlike multiple ago it is entirely text based which means that all of our interactions with it will
be through the command prompt.
So to begin we're going to load up the program.
There's two ways to do this.
We can either go to applications information gathering and select recon and from the menu or we can
load it up like a pro by opening up our terminal window and simply typing recon and
the first time you load the program you're going to get a lot of error messages about missing api keys.
I'll talk about that in a minute.
So let's go ahead and get started.
Recon and g is a web based framework.
It is entirely text based.
It was written by Tim tomes of Black Hills information security and IT functions very similar to existing
frameworks that you might already be familiar with such as Metis Floyd and social engineering toolkit.
So if you've used either of those before then using recon Angie will have the same feel and look to
it.
It is built around modules that include different functionality such as doing reconnaissance exploration
and discovery.
It's not a replacement for metal split or the social engineering tool kit.
It is focused on doing reconnaissance against a specific target very similar to how Montego is designed
to operate.
There are several Web sites that it uses to gather information.
Some of these sites are Google being linked in Facebook etc. It just depends on which modules you currently
have installed and which api keys you're using.
It works by sending queries to these sites to scrape open source information.
Recon energy is written entirely in the Python programming language so if you have any experience with
python you may be able to write your own custom modules fairly easily which can then be imported directly
into the existing framework.
The creator Tim has written an excellent developers guide for those wishing to get their feet wet in
this area and it includes a module template that you can use.
Check it out if you're interested in that side of things.
I should note before I begin that the current version of recon in G which comes pre installed with Kali
at the time of this recording is due to be upgraded several older modules for one reason or another
became defunct over time and were removed from the framework.
However replacements are currently in development.
Your version of recon and G.
May have additional modules not shown in this tutorial but hopefully after this class you will have
enough of a working understanding to be able to use the framework and pick up the ins and outs of any
newer modules that are released.
They all follow the same general pattern and principles so it should not be too hard to learn any new
ones.
You may even wish to upgrade to the latest version before you start to play around with it.
Just to take care of any bugs in the prepackaged version that comes with Kali.
You can do this by get using the Get Command to clone clone the latest repository from the recon Energy
Web site.
However be aware that if you decide to upgrade to the latest version it may be necessary to either update
or download the relevant Python libraries which as dependencies.
Otherwise you may encounter errors when you try to launch the program once loaded.
You will be presented with a text based title screen which is what you're looking at here.
Listing out all of the modules that come prepackaged with this tool.
Unlike multiple ago which was showcased in the last video recon energy is entirely text based.
All of the commands will be run through the prompt which tends to intimidate newer users who are not
as comfortable with this method of interaction.
It really is easy once you get the hang of it though.
The number next to each listed category is the number of currently installed modules yours may be different
than mine depending on your version.
Now before we begin actually using the program there is one major bit of setup we're going to have to
accomplish before we can actually use this tool.
As I said before recon and G perform searches through several different Web sites and some of those
sites require you to have an API key in order to perform the searches.
I'm not going to cover how to set up an account on each of those sites since they are constantly changing
and such information would quickly be out of date.
There are instructional websites online but really it's just as simple as setting up an account on say
flicker or LinkedIn or Twitter and then finding the API key listed under your account information.
I mentioned that these keys are required and you can see which ones are required by typing the keys
list command.
This will list all of the keys that you will need.
And again you will find them on the accounts page after you register for accounts but one thing I do
have to note there are a couple of these sites that require you to pay to get access to some of the
more advanced search features I mentioned this fact in the multi go module and it bears repeating here.
The good news is that if you decide you wish to invest to obtain those extra features your API key should
work for all open source intelligence tools that you use that call for them a bit a multi go recon energy
or whatever it is not necessary to actually spend money to get value out of these tools though.
But the advanced features are quite nice.
The interface to add your keys.
Once you've gathered them is very easy to use from within the framework itself.
As you've seen me do just type keys list to bring up the directory of modules that require keys
and then once you actually have your keys.
Just use the keys and command and then I'll do an example being API and we would copy paste our API
key.
The one I'm about to show you is not a real API key but it is representative of what one looks like.
They tend to be long nonsensical strings of letters and numbers.
Sometimes they're shorter than this.
The Bing Key was particularly long but some of them can be quite short.
And this is essentially what you would look for in your account information.
And some people get confused.
They register for example for a flicker account and they look in their account information for the API
key and they see where it's listed but then they see this long string of what appears to be nonsense.
This is actually what the key looks like.
So once we've entered it we just press enter these list and there we go.
It's input it and you would do this for each one of these modules.
Again some of them may require you to pay money when you register.
It's not absolutely required and the tool will function without all of the API keys.
So even if you're not able to use some of the modules that come with recon energy can still get a lot
of value out of it.
So I'm going to go ahead and I'm going to make a small cut to the video I'm going to add my own keys
and then we'll proceed okay.
I've got all of my keys installed and I've one thing I forgot to mention is that if you wish to add
a key that is not listed you can do that.
For example you could do keys add virus total API and then whatever your key might be.
And this is useful if you know that there is a particular module in development that calls for that
key and sometimes when you install module the entry for that key is not listed in the Keys list.
And I didn't spell Virus Total correctly but you get the idea as long as you name it whatever the module
expects it to be.
So for a virus total it would be a virus total API.
Then the module will check for it in the Keys list.
So this is just something to remember.
If you decide to upgrade later or if you decide to create your own modules and import them into recon
Angie
once you've got all your api keys entered we can get started by looking at the basics of the framework
here for the command prompt.
If you just type in the word kelp and hit enter we'll give you a list of the available commands if you
would like more information about what each command does.
Just type help and the name of the command and hit enter and this will give you case examples of how
to use it as well as any optional arguments that may be included.
For example help keys tells us that we can use the keys command with the arguments list add and delete
as we saw a moment ago.
The first command we want to try using is the show command.
This command will allow you to view items within the framework such as the included modules any data
that you have collected as well as the actual database schema you can use the tab completion to see
commands for example.
See all the commands that can be used with show type show and then press the tab key twice.
So for example if I wanted to show the banner I could do show banner
would help if I typed it correctly but a more useful demonstration of show would be to use the show
schema.
And this shows you how the various databases are setup all of the tables and columns for each one are
currently blank.
But as we begin to gather more and more information this tool these entries will start to fill up quickly
we'll be using show command a lot as we go along
so for now we're going to do show options.
These are all the global options that can be set for using the framework.
You can see that it already has several defaults set.
You can actually change these values either globally or for any of the individual modules that you'll
be using.
Using the set command.
So for example let's say that we wanted to change the threads.
We would do set threads and we'll do 20 show options we can see that threads have been changed from
the value of 10 to the value of 20
so as you can see it's pretty simple to use the name server that is listed as googles and DNS server.
Some of you may not like that.
And of course it can be changed.
You might wish to use the DNS server of a specific target to narrow down your search results.
You can change that option here.
So now let's drill down a little further we're going to use the clear command to bring up a fresh screen
and we're going to do show modules to give us a list of all of the available modules currently prepackaged
with this version of recon G rather a long list if we scroll up we can see everything
it's rather extensive and you'll notice that they're separated into categories
so we've got Discovery exploitation import recon etc..
It's quite a bit of output and that can be a bit of a pain.
So let's narrow it down to just what we want.
Show modules reporting
which will just show the relevant modules under the reporting category.
You can do this for any of the categories.
It can be helpful to remember this little trick until you really know what all the different modules
are and what they do as you're doing a particular research against a target.
You'll want to switch between the different types of modules very quickly.
We'll get into this a bit more later.
And one thing I'd like to note here you'll see this word default at the prompt.
This is not anything to do with the module you have loaded.
This is actually one of the work spaces that you can have loaded within the framework will cover workspaces
shortly.
But I wanted to point this out to avoid confusion.
You can also back out of a particular module by typing back.
So there's basically three ways to load a module from within recon and g the first two commands are
a use and load either one of these will work.
We could do load and just let's say
recon domains hosts being domain web and that brings up the Bing domain web module.
Now if we go back out of this for a moment if we know what the name of a module is and there aren't
multiple modules that use the same name we can just use the use command to very quickly load up a module
without having to type out the entire path such as with the load command.
So for example use profiler will bring us directly into the profile and profile our module.
And please note that the module you have loaded will always appear to the to the right of your workspace
in the prompt.
So the structure of the prompt is pretty simple it just tells you the first entry is that recon and
G is what we're working with.
The second entry which is currently default will show you the name of the workspace you're using.
Again more on that in a minute.
And the third entry will always be the module that you're currently running.
So on the subject of work spaces.
This is a quick concept I'm going to need to go over a workspace is basically just a separate location
that you can setup to store all of your data for a specific target.
And this would be handy if you're doing multiple tests against several different targets and it keeps
all of the databases that you build up within recon energy nicely organized.
You really don't want several different sets of data bases that are unrelated to exist in the same default
profile because then you'll start pulling up totally unrelated and dare I say highly wonky results.
So I'm just going to back out of profiler and clear the screen just to make things nice and neat.
So like I said this word default means that we're in the default workspace.
That's no good.
We don't want to use that or things will get very messy very quickly.
Let's go ahead and type work spaces list and hit enter and that'll bring up a list of the work spaces
that we have set up which is currently just default so to add a new workspace we're gonna do work spaces
add and you can call it whatever you want.
It's generally a good policy to name it after whatever your target is.
For instance if you were researching the Disney corporation you might want to name it Disney for right
now I'm just going to name it.
Class
that spit out a few errors because I don't have a complete list of API so I don't have the jigsaw and
POMALYST api keys entered.
But you probably won't get any errors and if you do it's no big deal.
So now if we do work spaces list again we can see that class has been added to our table.
Notice also that the prompt has now changed indicating that we are in the work space that we have just
created any data we enter or find using the various modules and recon Angie will be unique to this workspace
that will be separate from other workspaces that we create and will have its own databases that will
not bleed over when we conduct searches using other workspaces or the default workspace
so the last thing I'll say about work spaces for right now is that it's worth pointing out that whenever
you create a new workspace an actual folder for that workspace is created within the recon energy directory
and that folder will contain the unique database specific to that workspace that you built of over time.
So I'm actually going to back out of recon and G and I may do C.T. recon in G and if I do.
Alas can see there's a workspaces folder so will seedy workspaces unless again and there are work spaces
for class and default and within the class folder is our database.
So that's where it's stored.
If you want to make any changes if you want to take it if you want to take your database and import
it into recon and on another computer for example it's useful to remember these are the basic fundamentals
of using a workspace.
So with that all being said let's go ahead and restart recon and G OK and we'll go back to the workspace
that we created with Workspace select glass
and now we're in the class workspace.
So now we're ready to begin working with the actual modules to gather input from various domains and
use output for the hosts.
Now we're ready to begin working with the modules to gather actual data.
First off let's go ahead and list off the recon modules we're going to once again do show modules recon.
And we're going to scroll up to find our module
which in this case is going to be being domain Webb.
Actually this is a good moment to point out that each module the module center contains both its input
and output an information in this case it's going to be taking inputs from the domain tables and it
will put the outputs into hosts.
This will become more clear as we go along but it's just a little something to remember and come back
to it'll probably make more sense on a second viewing of this video which brings us to the obvious question
how do we input the basic information into our tables for the modules to use.
Oh there are a couple of ways that you can do this.
We can either set this on each module that we run or we can create a database entry with the add command.
For example if we use the ad command we can take the target domain and add it to the database for domains
so that every module we run will check against that listed domain.
So to do this we're gonna do ad domains and I'm just going to pick one Disney dot com.
And now we do show domains we can see that Disney dot com is now in our table of domains.
The other way to set the data once we have a module loaded.
If we go back and run let's say being a domain Web once we get that loaded if we do a show options command
we can see that there is only one input required here and this is where you would set your input.
If you have not already preset it to the relevant table.
So for example we would do set source Disney dot com or whatever your relevant information is that would
set it for this module alone.
But since we've already added it to the database manually via the domains table we don't actually have
to do this.
It's just a second way if you wanted to run a particular module using a piece of information that you
didn't want in your domains table for some reason maybe to keep your search results more narrow.
It's also worth pointing out at this point that you can get additional information about a module that
you currently have loaded by typing the show info command.
This shows you who wrote the module and gives a brief description of the module shows the options that
are needed.
And finally shows the database that will be queried even more fun.
You can do the show source command to see the code in Python.
That particular module runs with if you have coding skills.
This can be a veritable cornucopia of information about how the module works what exactly it is doing
and so forth.
You can see how each modules was written and you can use them as an example or a template when you write
your own.
Anyway now that our module is loaded and we have our data set.
In this case our domain.
We just need to run the module to do this.
We just type the run command and hit enter.
This may take some time.
If you have a domain with a lot of subdomains and I suspect that Disney has a lot of subdomains
this information as it's being gathered is being added to our tables each green asterisk next to an
entry represents a new piece of information a blue asterisk is either notifying you of something or
telling you that a piece of information that is already present within the tables has been found you'll
also notice that it will sleep to avoid lockout.
That's because there's a limited number of search queries with some of these modules.
It can slow this process down a little bit but I recommend that you not change that setting.
It can be very annoying to be locked out completely and lockouts can last up to I believe 24 hours.
It may have gone up to 48 with some Web sites that recon and she queries.
You also won't necessarily be told if you get locked out.
So if you find that your search queries are running and you're not getting any results and you know
you should be consider trying again after about 24 hours of past if you've been running a module excessively
against certain Web sites without limiting your thread count.
All right.
So it looks like we found quite a lot of information.
So if we do these show hosts command
and we pulled up quite a lot of subdomains.
Now you'll notice that at the moment we only have the name of the host.
The row I.D. and the module that was used to find it the IP address region country and coordinates are
not yet included but we'll be getting those pretty soon now.
We could have done this all manually we could have looked up each one of these and added them to a table
individually just like this.
That's the beauty of open source intelligence programs.
All of this information is available out there.
However as we go along our database tables will improve as more and more information fills up inside
them.
And for this reason it is sometimes advantageous to run the same module several times at different points
during your research process.
We just ran big being web domain.
Now if we run some of the other modules that relate to finding hosts and finding domains then our tables
will improve those modules may find things that Bing domain Web did not find.
And then if we go back and run Bing domain Web again later in this process we may get still more results.
But that's just something to keep in mind we don't need to worry about being that fastidious just for
this tutorial.
So now let's go ahead and start filling in those additional fields that I mentioned such as IP address
region and country et cetera.
We'll start by focusing on how to get a hold of the IP address for the host.
There's a good module for this we can use that as cold resolve so we'll just use resolve.
Pardon me use recon hosts hosts resolve would help if I spelled it right.
Wouldn't it.
There we go.
OK.
Sorry about that.
So we have the module loaded.
Let's go ahead and run it
and we can see that it's pulling up IP addresses for each of those subdomains that we found or hosts
rather pardon me.
So now if we do show hosts Well there we go.
We now have all of these IP addresses included in our database.
So now let's go ahead and fill in the rest of those blanks.
We have the IP address.
Let's find out where on earth that corresponds to.
There's a useful module for this.
We'll use free geo ip and if we do show info you can see that it uses IP addresses as the input since
we already have that in our database.
All we need to do is type run.
And again you could set this individually if you wanted to limit your results to a single IP address
you would use the set command here and just simply use a single IP.
But we're gonna go ahead and check them all and now it's pulling up location data.
Now if we do show hosts again while our table has become a little bit muddled and that will happen we
can make this pretty later.
Don't worry.
But for right now we can see that almost all of these produced a result we have the location country
latitude longitude
hopefully this example gives you an idea of how you develop information about your target.
The more information you uncover the bigger your databases become more your subsequent usage of various
modules will uncover so it may seem tedious at first starting with just a small amount of information
like but like a row of falling dominoes one thing leads to another pretty quickly and pretty soon your
search will blossom into a large trove of information before even before you know it they'll have a
huge picture of the activities of your target locations habits all of this data is coming without having
to set foot on their property or sending any packets to their servers.
It's all open source so let's take a look at the other tables in the database.
The locations if we do a quick show locations we can see that it currently does not have any data.
One of the other modules we want to use is the reverse geo code using the latitude and longitude that
we have already obtained.
So the module that we were going to use for this is called
reverse geo code
where you show info you can see that it needs latitude and longitude which we already have.
I think we need to add them individually for this one but let's go ahead and try running it first.
This may not work.
Yeah it has to be added individually some modules will not automatically check your database if you
get an error like this.
You will have to add the individual pieces of information to the module.
It's just the way the module is designed.
So we're going to add some of these two are locations table so we do add locations.
And I'm just going to do one of these to start out with.
We're going to do our latitude.
We will copy it.
And paste
and now we're going to do our longitude.
Same deal copy
paste.
We don't have the street address yet.
That's what we're trying to find out so we're gonna leave this blank.
We'll just press enter and now we're gonna go ahead and run it.
OK.
Show hosts I'm sorry show locations.
And there we go.
Now we have an actual street address to go with that information so as you can see this is pretty easy
sometimes.
These modules will not pull up the relevant information I actually had that happen during a previous
attempt to record this class where a couple of these a latitude and longitude just simply did not produce
a result and that was simply a failure of the module.
But in the vast majority of cases you will get information back.
So just be patient.
Keep trying it does occasionally take multiple tries.
If a module fails it doesn't hurt to run it twice.
I've actually had it succeed on a second attempt.
So here we go all the basic information we were looking for.
All right.
So the next table we're going to look at is called push pins.
This is one of the more fun aspects of recon and gee it's also one of the creepier aspects of recon
energy and open source intelligence in general and you'll see why shortly with push pins Well we can
collect data from sites like flicker YouTube Instagram and we can actually put that info up on a map.
For example if you use push pin module for flicker it will connect to flicker using the GOP data that
we have already obtained and pull down any photos related to that particular location within a certain
radius of it.
It will take the data and plot it out for you on the map.
So we'll show you what I mean.
We're going to go ahead and we're going to use flicker
and we'll do show info you can see that it requires inputs from latitude and longitude which we have
already input it.
We could put in more but that would result in a lot of options and it would take a lot of time.
So for simplicity's sake we're just going to use the one set of coordinates and now we're just going
to go ahead and we're going to run this module
and we can see that it's finding a lot of photographs that are associated with this set of coordinates
and this number would be a great deal more if we were using all of the coordinates that we had pulled
up.
And it's true that not all of these would be relevant and I should also mention that this is being done
through the API key that we entered for flicker worked 1000 photos already.
As you can see this takes some time and if you're using a lot of locations it will take even longer.
It's generally best to keep your search somewhat narrow if you include many disparate locations your
map information is going to be a jumbled mess.
I'm actually going to go ahead and make a pause to the video once we get up to about a foul 3000 photographs
just in the interest of not taking up too much time with this process.
OK.
Well four thousand two hundred and six total push pins were found or thirty three thousand two hundred
and fifty photos Yeah I am I will say that you won't normally find this many from a search.
And the reason this number is so high is because Disney in any case this will certainly do for an example.
So now that we have the data let's go ahead and run one of the reporting modules and see what it looks
like when everything is nicely plotted out on a map.
So
let's go ahead and use reporting push pen show options
so we're going to narrow down our search a bit more by getting specific latitude and longitude that
we used for
just this location
set latitude
we can copy and paste
set the longitude.
Pardon me for being imprecise
and now we don't want to come up with an excessive number of results because we got a lot of push pens
from this search and once again you will not find so many in the vast majority of cases only with very
large corporations such as Disney would you tend to find so many push pens.
So we're going to set the radius of our search to one and that will narrow down the results to the specific
area on the map and now we're gonna go ahead and run it.
Now it's going to open our browser window.
And forgive me that this is excessively slow sometimes.
This module is very slow to assemble a map particularly with so many different push pin results and
photographs to plot so it's creating the map.
Now it should just take a moment and here we go.
We can see that all the data has been plotted out on the map.
Two different windows that go with this particular module.
This is the media reporting.
You can scroll down this list and see the individual entries and there's the push pins map.
And this is the radius that we set radius 1.
So everything within this radius is relevant to our search.
Now again you won't get this many results.
I chose Disney and that's why we're seeing so many different geo tags.
A smaller company will definitely have more focused results.
And this is what I meant earlier when I said this is kind of creepy because if you know what you're
doing you can actually track people down like this.
You can see in essence where they've been where they took a particular photo.
You can track their patterns and their movements.
And this is the way the Internet in the way of open source intelligence gathering.
People are just not careful about what they post online and they're not sensible about what information
might be included with those posts even geo tags for simple photographs.
And of course we could click on individual pins and get more information but you get the general idea.
Also this module that we're using was just limited to flicker but if we included for example the Instagram
module this would be also included down here and we could uncheck a particular module in this case flicker
tune again get rid of all of the plotted results for that module to help narrow things down further.
And so as you can see there is a wealth of information that can be pulled up with recon energy and like
the multi go tutorial.
This is really just scratching the surface of what you can do if you practice and play around with this
tool.
I guarantee you'll be able to pull up far more information than this and all of this is open source.
It's free.
It's nicely organized for you.
And as you play around with the various modules you'll be able to find ultimately almost any piece of
information that you might be looking for on either a person or a company.
It's all out there.
So I'm going to close this for the moment and the last aspect of recon energy I want to touch upon before
I close out this introduction is the use of snapshots snapshots.
Essentially let you take a quick backup of your current workspace.
You can then restore from a snapshot if you need to.
So let's say for example that you've gathered a lot of data and now you want to run a new experimental
module that you've never run before.
This module might corrupt your database with a lot of useless junk.
So before you run that you might want to take a snapshot of your current workspace and backup all your
databases very quickly so that you can revert back if anything goes wrong.
So help snapshots
sorry need to be in the right context menu help snapshots gives us our arguments.
So we're gonna do snapshots list.
We don't have any yet no notice workspaces no snapshots so snapshots take if we list
sorry.
We can see that we now have one that we could load up if we needed to
and it's as easy as that.
And you can take multiple snapshots throughout a reconnaissance project all for the same workspace if
at any point you find that a particular search has given new york databases an influx of completely
irrelevant information which can happen which is then cluttering up your searches.
It's very easy to revert back without having to start the entire process over again in a new workspace
or having to edit your databases which let's face it can be quite painful.
Before I close out this section of the tutorial though I'd like to show you what you can do with all
of this data.
Once you've assembled it so it's actually very easy to take all of this disparate information and assemble
it into a a nicely readable format.
So what we're gonna do is we're gonna use one of the many reporting modules that comes with recon energy
and this will assemble all of that data for you.
So let's go ahead and first off show and launch rules reporting we have quite a few choices.
I'm going to use the H Tam l version use reporting punched in the mouth and now we're gonna do show
options so we're gonna set it creator to Udemy the customer student.
And as you notice the file name is the path where the report will be generated.
So in this case it would be placed in the work spaces folder that we've created under recon and G but
I'm going to change that to the desktop set
route desktop Disney dot HD PML and now we're gonna go ahead and run the reporting module and this is
generated the report for us.
So I'm going to minimize recon and G in here it is and then a double click this and this will open up
the file in our web browser.
And here we go.
A nicely assembled report of all of the information that we've pulled up.
Now of course we only ran a few of the modules that came with recon energy which is demonstrated in
the summary here and in the categories that the report generated for us.
So we can see from our search all of the hosts that we found their coordinates their locations the fact
that we which which module we used
we can see which domains we searched which in this case was only the one
the locations that we pulled up
and as you can see from the summary a great deal of information can be assembled.
And this is of course what you're seeing is limited to the modules that came prepackaged with recon
energy.
I mentioned at the start of this tutorial that the Facebook and linked in modules are currently being
recreated as it were as they had some problems.
So with those modules in use as well as others you can generate a picture of your target.
That would include all of the employees in a particular corporation how they interrelate their contacts
their credentials and you can take this information and you can run it through other open source intelligence
tools to see how individuals within a corporation interrelate.
That's a very good use of multi go to see how the credentials linked to specific individuals and so
forth.
So really the sky is the limit in terms of what you can discover about corporations people really anything
you can search for.
And as you find more information you're able to refine the questions that you ask.
And this is very important.
If you look into something in a very general way you're likely to pull up a great deal of information
and not a lot of it will be really useful.
But as you assemble a picture you can focus your search.
And by doing that you can really find out the inner details that you really want to know.
So going to go ahead and close out of the reporting module for the moment and I'm going to show you
one final tool of recon Angie and that is the ability to run scripts.
So this script is very simple it's just a list of all the commands that you saw me run during the tutorial
and you can actually load recon energy using this script or any other script that you write and it will
automatically run through each of these steps one by one it can be very handy if you're conducting research
against multiple different targets to have these scripts you just load an instance of recon energy with
one script and then you can load another and all you would do is we might change the name of the workspace.
So anyway it's a useful thing to know so I'll demonstrate it now.
So to show this off we're in a fresh instance of recon energy and the command that we're looking for
is called resource.
So we're going to help resource in the root context menu and we can see that the resource command simply
requires a file name in this case the path to the script that we want to run.
So we're going to do resource groups desktop and I named it script and we press center
and now it's going to run through all of the commands one by one that you saw me use throughout the
course of this tutorial.
And it's not really necessary to showcase all of this.
You get the idea.
And when this concludes a report will be generated on the desktop just as before.
Because I told the script to do that.
So it's not really necessary to showcase all of this is this is all something you've seen.
So I will close out the tutorial here.
I hope you enjoyed it and that you have a lot of success with recon Angie.
Thank you.