WEBVTT - This file was automatically generated by VIMEO

1
00:00:06.800 --> 00:00:09.400
 So now that we have an emulator setup, we are

2
00:00:09.400 --> 00:00:12.500
 able to start to work on building our test environment

3
00:00:12.500 --> 00:00:15.400
 on the actual phone itself. And for this

4
00:00:15.400 --> 00:00:18.700
 I'm going to discuss. Who would have been about how to use ADB to give

5
00:00:18.700 --> 00:00:21.200
 you a little bit of fundamentals, on. And we'll also take

6
00:00:21.200 --> 00:00:27.100
 a look at installing a purposefully van Ripple application applications

7
00:00:24.100 --> 00:00:27.200
 that

8
00:00:27.200 --> 00:00:30.400
 I'm going to be using. In this one of them, is going to beat

9
00:00:30.400 --> 00:00:33.800
 this one here. It's called Diva and I'll

10
00:00:33.800 --> 00:00:37.000
 include these links inside of like a resources section

11
00:00:36.300 --> 00:00:39.300
 at the end of the course. And that

12
00:00:39.300 --> 00:00:42.600
 way you'll be able to access all of these links as discussed.

13
00:00:42.600 --> 00:00:45.500
 And I'll discuss with your videos. The links are actually

14
00:00:45.500 --> 00:00:48.200
 utilized in that sort of thing. Just that what you're able to access

15
00:00:48.200 --> 00:00:52.700
 them without having to type this out word for word. So once

16
00:00:51.700 --> 00:00:54.100
 we download this will be able to get

17
00:00:54.100 --> 00:00:57.300
 in a pique and I APK will be able to be installed

18
00:00:57.300 --> 00:01:00.100
 on the device. I have another APK which is

19
00:01:00.100 --> 00:01:03.100
 insecure Bank V2, and this is another APK that

20
00:01:03.100 --> 00:01:05.400
 will install it another insecure application.

21
00:01:05.800 --> 00:01:08.300
 I'll post the link for this inside of a resource is

22
00:01:08.300 --> 00:01:11.200
 section. In this course that you're able to get access to that.

23
00:01:11.200 --> 00:01:14.200
 And download the APK says, well, it's the very

24
00:01:14.200 --> 00:01:17.200
 first thing them discusses. If you're following Along on your own

25
00:01:17.200 --> 00:01:20.500
 Android device. If you aren't using an emulator, you're going to first, have

26
00:01:20.500 --> 00:01:24.000
 to enable USB debugging and to

27
00:01:23.200 --> 00:01:26.700
 do this, you're going to go into your settings and you're

28
00:01:26.700 --> 00:01:30.000
 not to get access to the developer tools to

29
00:01:29.200 --> 00:01:32.300
 do this. It's a little bit tricky, you have to go into

30
00:01:32.300 --> 00:01:35.200
 your system, and they have to go to about

31
00:01:36.600 --> 00:01:39.900
 I need to scroll down to build number and you're

32
00:01:39.900 --> 00:01:42.200
 just going to tough on this until it

33
00:01:42.200 --> 00:01:45.100
 says, you are now a developer. Once this is

34
00:01:45.100 --> 00:01:48.800
 done. You should know how have a developer tools auction

35
00:01:48.800 --> 00:01:51.800
 in your settings. And on

36
00:01:51.800 --> 00:01:54.500
 this one here. I restart

37
00:01:54.500 --> 00:01:56.400
 my settings to make sure that it shows.

38
00:01:59.900 --> 00:02:02.300
 If you can't find it, you

39
00:02:02.300 --> 00:02:05.700
 can try like typing it in here. You'll see developer options

40
00:02:05.700 --> 00:02:08.100
 Thunder system and then developer options in

41
00:02:08.100 --> 00:02:12.200
 this case. So yeah under system and then

42
00:02:12.200 --> 00:02:16.100
 there should be a Developer Options under Advanced. It

43
00:02:15.100 --> 00:02:18.300
 will be in different locations, depending on your device.

44
00:02:18.300 --> 00:02:21.100
 These this way, just to search it in your settings, to find a

45
00:02:21.100 --> 00:02:24.200
 developer settings, access to

46
00:02:24.200 --> 00:02:28.000
 a lot of different things that are commonly used by application developers

47
00:02:27.300 --> 00:02:30.200
 and Ally. B. Settings may be useful for you

48
00:02:30.200 --> 00:02:33.400
 while debugging applications or trying to test them for the

49
00:02:33.400 --> 00:02:36.500
 moment. They were interested in right now is USB debugging. You

50
00:02:36.500 --> 00:02:39.500
 want to make sure that USB debugging is enabled and it

51
00:02:39.500 --> 00:02:42.200
 when this will allow you to access your device through the

52
00:02:42.200 --> 00:02:44.900
 command line of your computer using the ADB tool.

53
00:02:45.700 --> 00:02:48.200
 This is wanting to know if you're on like an

54
00:02:48.200 --> 00:02:51.300
 emulator, you won't talk s*** to do this stuff cuz it comes enabled by default.

55
00:02:51.300 --> 00:02:54.200
 So from here, we can launch

56
00:02:54.200 --> 00:02:57.500
 up our command line and we can take a look at how we can access

57
00:02:57.500 --> 00:03:00.300
 our device through the command line. So there

58
00:03:00.300 --> 00:03:03.300
 is a tool called a dbe which is installed typically with

59
00:03:03.300 --> 00:03:06.400
 Android studio. And as a whole bunch of different tools that

60
00:03:06.400 --> 00:03:09.200
 allow us to manipulate our device and

61
00:03:09.200 --> 00:03:12.500
 be able to install different apks. For

62
00:03:12.500 --> 00:03:15.500
 instance of creating content providers is another common

63
00:03:15.500 --> 00:03:18.900
 thing. There's a lot of things that this is very useful for when

64
00:03:18.900 --> 00:03:21.900
 the main things is getting a shell, into your device,

65
00:03:21.900 --> 00:03:24.500
 to be able to navigate through it,

66
00:03:24.500 --> 00:03:27.200
 and to download pieces and all that good

67
00:03:27.200 --> 00:03:31.100
 stuff, right? So if you type in a TB devices,

68
00:03:33.200 --> 00:03:36.400
 In this case, it just had to

69
00:03:36.400 --> 00:03:39.300
 kill off the client and then started again, but you'll see

70
00:03:39.300 --> 00:03:42.400
 he'll give us a list of devices that are currently attached

71
00:03:42.400 --> 00:03:45.100
 to a computer so that we have one device which is

72
00:03:45.100 --> 00:03:48.100
 the emulator. So if I were to type it out

73
00:03:48.100 --> 00:03:51.200
 ADB shell with, this will do, is it

74
00:03:51.200 --> 00:03:54.100
 will create a shell into the device itself. So you can

75
00:03:54.100 --> 00:03:57.800
 see. Now we have a shell on the device by typing something like LS printable

76
00:03:57.800 --> 00:04:00.400
 list of directories sis is like a classic sort

77
00:04:00.400 --> 00:04:04.100
 of computer. She'll just on a mobile device instead. So

78
00:04:03.100 --> 00:04:06.400
 this is one thing that's very nice to be able to do with ADB

79
00:04:06.400 --> 00:04:10.000
 it to be able to Shell on to the device, to gather information.

80
00:04:09.700 --> 00:04:12.100
 For instance, to be able to like find out

81
00:04:12.100 --> 00:04:16.000
 where an optimist installed navigate to a specific directory

82
00:04:15.100 --> 00:04:18.400
 that were trying to access. Or, you know,

83
00:04:18.400 --> 00:04:21.200
 just cdata that's all the device. I wanted that you might not

84
00:04:21.200 --> 00:04:24.600
 have permissions to give her a rooted device will be able to escalate yourself

85
00:04:24.600 --> 00:04:27.500
 to route and get permissions to these aspects. But um, yeah,

86
00:04:27.500 --> 00:04:30.400
 typically, you won't have permissions to everything if we're

87
00:04:30.400 --> 00:04:33.000
 trying to do this as a legitimate user, we typically

88
00:04:33.100 --> 00:04:36.200
 Because you want to be able to do things, any sort of user would

89
00:04:36.200 --> 00:04:36.900
 be able to do.

90
00:04:37.800 --> 00:04:40.200
 So that's one thing they were able to do with ADB and

91
00:04:40.200 --> 00:04:44.600
 if I take an exit, it will take me out of this. She'll know. What

92
00:04:44.600 --> 00:04:47.200
 I really want to do is I want to instill these two apks that

93
00:04:47.200 --> 00:04:50.100
 we have a download it so that we could do this

94
00:04:50.100 --> 00:04:53.100
 is all CD to the directory. And then what

95
00:04:53.100 --> 00:04:56.700
 I can do is I can type in a DB install and

96
00:04:56.700 --> 00:04:59.700
 I type in the name of the APK is here

97
00:04:59.700 --> 00:05:02.800
 will say performing streamed install and then six and all

98
00:05:02.800 --> 00:05:05.700
 you see on my device. I should

99
00:05:05.700 --> 00:05:08.400
 have the I have the diva app available now so

100
00:05:08.400 --> 00:05:10.800
 you can see that install the application for us.

101
00:05:11.600 --> 00:05:13.900
 And then I can do the same with the insecure Bank.

102
00:05:15.300 --> 00:05:18.100
 And you can see that that will install the app as well. So that's the

103
00:05:18.100 --> 00:05:21.600
 main thing that we're looking to do with ADB, just get beat you up applications installed

104
00:05:21.600 --> 00:05:24.400
 another. You have these two applications installed,

105
00:05:24.400 --> 00:05:27.500
 you'll be able to know follow along,

106
00:05:27.500 --> 00:05:30.500
 with all the different situations that we do with those two apps. So

107
00:05:30.500 --> 00:05:34.000
 these two jobs, again, have purposefully insecure setups,

108
00:05:33.400 --> 00:05:36.200
 which will allow us to sort of manipulate through

109
00:05:36.200 --> 00:05:39.500
 them and attempt to attack them, as you would, maybe a taco. But

110
00:05:39.500 --> 00:05:42.500
 you to meet up with kishin soap, using this will be able to discuss

111
00:05:42.500 --> 00:05:45.500
 if it up like the ideology of attacks and be able

112
00:05:45.500 --> 00:05:48.700
 to actually practice it on legitimate applications, right?

113
00:05:48.700 --> 00:05:51.500
 So this will get you set up without the

114
00:05:51.500 --> 00:05:54.900
 things that you need to be able to follow along on the emulator. So

115
00:05:54.900 --> 00:05:57.700
 from here, we'll be discussing the actual concepts related to

116
00:05:57.700 --> 00:06:00.400
 Android. Vulnerability analysis in Android, pentetate

117
00:06:00.400 --> 00:06:01.500
 penetration testing.
