So we can see here from the result, it was able to find a number of files, some of them we already
know of now, the five icons, just an icon further and.
These are probably only style files.
Index is the index that we see usually.
So it's all right.
Log in.
We can see that we discovered a page that allows people to log in.
Now, in many scenarios, I was able to find username and password of a target exploit in a really complex
exploit and then ended up not being able to log in because I couldn't find where to log in.
So tools like this could be very useful.
And here we can see that we have a login page that we can use to log in.
Patient often never is not very useful.
You can see the full file now, this file is usually very, very useful because it displays a lot of
information about the BHP interpretor running on the Web server.
And as you can see, this file contains a lot of information, a lot of them are useful now you can
see you get to know some of the directories, you know that it's running five.
The configuration is stored in this file.
Unifiers is usually the config files for HP, so you can see all the places where they're stored.
And going down, you'll see all the permissions they installed and we can see here, it has my excuse
also it's used in my school and you can see that there are directories where different types of configurations
are stored.
You can also see all the modules and extensions that are being used with.
So this file is usually very, very useful.
You can see we managed to find where my admin login is, and that's basically the login that's used
to log into the database.
Another very useful file is the robots that Steve, and that is the file that tells search engines such
as Google how to deal with the website.
So it usually contains files that we don't want the website or Google to see or to read so we can read
that file.
Then we'll be able to see what what the Web admin is trying to hide.
So go in and hear.
We can see that the Web admin doesn't want Google to see a directory called Password.
OK, and it also doesn't want to see a file called Conflict Dot Inc.
And also doesn't who wanted to see these other files, so let's have a look on the passwords and the
conflict as examples.
So I'm just going to open a new tab.
And we're going to put our address like so.
So it's the current directory and then we just put passwords after.
And that we can see that there is a file called I can still text.
And going here, we can see that we got some usernames and passwords, so we can see there is admin,
admin plus we can see that we have a password as Adrian and some password.
So we managed to find usernames and passwords.
Now we're still not sure what these usernames and passwords for, but we're sure that we were able to
find very useful stuff.
Another useful file is the config, that ink.
So let's see what's in that.
And from here, we can see that we have.
Information that allow us to connect to the database, because these are saying Debe helps the user
pass and name so we can see that the user name is route and the password is blank, so we can go ahead
and try to connect to the database based on these commands, and then we should be able to get access
to the database.
Also, using these passwords, we're still not sure what we can use them for, but we can add them to
at least try to log into the admin or just store them in a list so that we can use it if we're going
to do any brute force attack.
So then again, this is another video that just shows how important and powerful information gathering
can be.