1 00:00:01,040 --> 00:00:02,170 Welcome back. 2 00:00:02,340 --> 00:00:12,360 In today's lesson we are going to analyze how the pecker protects the program so too do they have to 3 00:00:12,840 --> 00:00:16,290 both fast I will start with this one. 4 00:00:16,300 --> 00:00:18,730 Yeah and back version of Trekkie. 5 00:00:18,880 --> 00:00:28,330 And then I will patch it and then repeat the same thing is the penguin and see whether it works or not. 6 00:00:28,330 --> 00:00:35,350 So now let's say so I open the unpacked version with excessive for DVD 7 00:00:38,630 --> 00:00:39,730 and then run it 8 00:00:44,600 --> 00:00:47,160 into anything kitchen 9 00:00:51,860 --> 00:00:55,400 now have tossed in the button. 10 00:00:57,910 --> 00:01:05,720 Taking on the costing using more you should be this one to the far right click photo front. 11 00:01:06,550 --> 00:01:15,820 And now we come to this address in No did he have said this before in a previous earlier lesson. 12 00:01:15,820 --> 00:01:17,580 So he took forward. 13 00:01:17,680 --> 00:01:18,560 How do you do this. 14 00:01:19,090 --> 00:01:21,310 Fiscal and revise. 15 00:01:21,400 --> 00:01:24,600 So now time is here and you see there is a jam here. 16 00:01:26,340 --> 00:01:34,170 And this jam if he jumps it jump to the good message if he doesn't jam we show you the impact message 17 00:01:35,230 --> 00:01:36,770 so this and Breakpoint here. 18 00:01:39,300 --> 00:01:39,910 KING On run 19 00:01:43,380 --> 00:01:45,820 king Okay picture again. 20 00:01:46,260 --> 00:01:53,510 And now it has stopped any break point and you see jam is not taken that means he is going to show you 21 00:01:53,630 --> 00:01:55,200 that message. 22 00:01:55,200 --> 00:02:05,100 So in order to prevent me from showing you that message the issue assemble and jam here making jam. 23 00:02:05,430 --> 00:02:06,960 So we assembled a jam here 24 00:02:10,660 --> 00:02:16,280 yen B check size trashes inside okay. 25 00:02:17,590 --> 00:02:17,900 You. 26 00:02:18,740 --> 00:02:26,390 So now the jump should take place soon known as press f it heavy press. 27 00:02:26,390 --> 00:02:27,480 Fitting in. 28 00:02:30,400 --> 00:02:34,130 Now the good message has shown karaoke. 29 00:02:34,490 --> 00:02:42,110 So we are just trying these subway now less batches so please file batch file. 30 00:02:43,160 --> 00:02:46,480 And this is the best we are going to make. 31 00:02:46,660 --> 00:02:55,450 So take pass file and then give it in Union. 32 00:02:55,960 --> 00:02:59,330 And in that here put a dash C patch 33 00:03:02,570 --> 00:03:07,040 DC to gain losses. 34 00:03:07,160 --> 00:03:08,190 Now let's try to run it. 35 00:03:12,120 --> 00:03:12,460 Right. 36 00:03:15,560 --> 00:03:16,400 Enter anything 37 00:03:19,220 --> 00:03:20,450 so our patch works. 38 00:03:20,750 --> 00:03:26,660 Okay now let's try to do with the penguin so I'll close the debugger 39 00:03:30,980 --> 00:03:34,350 and open the path vision. 40 00:03:34,580 --> 00:03:35,750 Excessive for the 41 00:03:40,080 --> 00:03:41,800 and now run 42 00:03:45,300 --> 00:03:58,910 enter anything check wrong key So please pass anything click on casting and insert the user module column 43 00:04:00,140 --> 00:04:07,670 rightly photo from and it comes at the same pace as before. 44 00:04:07,910 --> 00:04:10,030 Now this gem should take place. 45 00:04:10,820 --> 00:04:13,600 So we are going to assemble a gem here. 46 00:04:17,260 --> 00:04:19,480 So assemble a gem GMP 47 00:04:23,300 --> 00:04:25,930 OK first. 48 00:04:26,530 --> 00:04:28,660 So another jam is here. 49 00:04:28,660 --> 00:04:29,520 It should be a.. 50 00:04:30,300 --> 00:04:32,070 So another script run 51 00:04:34,780 --> 00:04:37,360 off key feature again. 52 00:04:37,720 --> 00:04:38,740 Key. 53 00:04:38,870 --> 00:04:39,150 All right. 54 00:04:39,170 --> 00:04:39,550 Sylvia. 55 00:04:39,560 --> 00:04:43,950 Now managed to create this a bank version. 56 00:04:44,480 --> 00:04:48,080 Now let's try to patch it see what happens. 57 00:04:48,110 --> 00:05:01,700 So if you file deep bench and we see patching the same thing like before this instruction fetch and 58 00:05:01,700 --> 00:05:03,900 yet giving name back 59 00:05:07,130 --> 00:05:07,700 fetch 60 00:05:13,510 --> 00:05:19,440 say 80 0 0 1 fetch a pay. 61 00:05:19,940 --> 00:05:21,350 We are not able to touch it. 62 00:05:22,220 --> 00:05:23,170 OK. 63 00:05:23,390 --> 00:05:28,410 You're not able to budget rescue OK do it. 64 00:05:29,720 --> 00:05:39,950 If he discusses the United child you run is Bashar getting run. 65 00:05:44,060 --> 00:05:46,970 Anything any fears. 66 00:05:47,870 --> 00:05:48,440 He feels 67 00:05:51,180 --> 00:05:58,400 if you trust is this value and you open your pacifier you evaluate 68 00:06:02,460 --> 00:06:03,890 the same thing. 69 00:06:03,900 --> 00:06:04,560 He can run 70 00:06:07,350 --> 00:06:28,710 into check key parts cost say goes to the follow from to and noticed as he fails to patch the assembly 71 00:06:28,760 --> 00:06:33,250 did the GMB but he feels a patch. 72 00:06:33,250 --> 00:06:34,930 So that's why you work. 73 00:06:35,560 --> 00:06:45,880 So as you can see the pay phone has prevented the developer from patching the file. 74 00:06:46,720 --> 00:06:51,200 So this is how it protects the software from being cracked. 75 00:06:51,220 --> 00:06:54,310 He added You are not able to patch it. 76 00:06:54,400 --> 00:06:58,510 This is how so hypotension was using packing. 77 00:06:58,660 --> 00:07:07,220 So in the next video I'll show you how to bypass the protection using the unpacking method. 78 00:07:07,630 --> 00:07:11,680 So I'll see you in an SS and thank you for watching.