So now that we have an emulator setup we are able to start to work on building our test environments
on the actual phone itself.
And for this I'm going to discuss a little bit about how to use ADP to give you a little bit of fundamentals
on that.
And we'll also take a look at installing a purposefully vulnerable application.
Now the vulnerable applications that I'm going to be using in this one of them is going to be this one
here.
It's called diva.
And I'll include these links inside of like a resources section at the end of the course.
And that way you'll be able to access all of these links as discussed and all I'll discuss which video
is the links are actually utilized in that sort of thing just that way you're able to access them without
having to type this out word for word.
So once we download this we'll be able to get an API K and that AP K we'll be able to be installed on
that device.
I have another AP K which is in secure bank V2 and this is another AP K that will install lots and other
insecure application.
Again I'll post the link for this inside of a resources section in this course that you're able to get
access to that and download the AP case as well.
So the very first thing that discusses if you're following along on your own Android device and you
are using an emulator you're going to first have to enable us to be debugging and to do this.
You're going to go into your settings and you're can have to get access to the developer tools to do
this it's a little bit tricky.
You have to go into your system and then you have to go to a boat and then you just scroll down to build.
No.
And you're just going to tap on this until it says you are now a developer.
Once this is done you should now have a developer tools option in your settings.
And on this one here I restart my settings to make sure it shows
if you can't find it you can try like typing it into care.
You'll see developer options.
It's under system and then developer options in this case.
So yeah under system.
And then there should be developer options under advanced it will be in different locations depending
on your device.
The easiest way is just to search it in your settings to find that developer settings.
So it's not here you build to get access to a lot of different things that are commonly used by application
developers and a lot of these settings may be useful for you while debugging applications or trying
to test them.
But the main one when they're interested in right now is us to be debugging.
You want to make sure that us be debugging is enabled enabling this will allow you to access your device
through the command line of your computer using the ADP tool says it's one thing to know if you're on
like an emulator you won't actually have to do this step because it comes enabled by default.
So from here we can launch up our command line and we can take a look at how we can access our device
through the command line.
So there is a tool called ADP which is installed typically with Android Studio and it has a whole bunch
of different tools that allow us to sort of manipulate our device and be able to install different AP
case for instance of querying content providers is another common thing.
There's a lot of things that this is very useful for.
One of the main things is getting a shell into your device to be able to you know navigate through it
and to download pieces and all that good stuff right.
So if you type an ADP devices
in this case it just had to kill off the client and it started again but you'll see Oh give us a list
of devices that are currently attached to our computer.
So in this case we have one device which is the emulator.
So if I were to type in now EDP shell what this will do is it will create a shell into the device itself.
So you can see now we have a shell on the device.
If I type in something like a less for insensible listed directories.
So this is like a classic sort of computer shell just on a mobile device instead.
So this is one thing that's very nice to be able to do with ADP is to be able to shell onto the device
to gather information for instance to be able to find out where an app is installed or navigate to its
specific directory that we're trying to access or you know just see data that's all the device.
All of this you might not have permissions to.
If you have a routed device you'll be able to escalate yourself to route and get permissions to these
aspects.
But typically you won't have permissions to everything.
If we're trying to do this as a legitimate user we typically don't want route because we want to be
able to do things that any sort of user would be able to do.
So that's one thing that we're able to do with ADP and if I type an exit it will take me out at the
show.
Now what I really want to do is I want to install these two AP case that we have downloaded.
So one way that we could do this is all C.D. to the directory and then what I can do is I can type in
ADP install and I type in the name of the peak is you will say performing streamed install and then
success and you'll see on my device I should have the I have the diva app available now.
So you could see that installed the application for us and then I can do the same with the insecure
bank and you can see that that will install the app as well.
So that's the main thing that we're looking to do with ADP is just get these two applications installed
and now that you have these two applications installed you'll be able to now follow along with all the
different tutorials that we do with those two apps.
So these two apps again have purposefully insecure setups which will allow us to sort of manipulate
through them and attempt to attack them as you would maybe attack a legitimate application.
So using these we'll be able to discuss a bit of the ideology of attacks and be able to actually practice
it on legitimate applications.
Right.
So this will get you set up with all the things that you need to be able to follow along on the emulator.
So from here we'll be discussing the actual concepts related to Android vulnerability analysis and Android
penitent penetration testing.