Hello In this lesson I would like to summarize and reinforce the software cracking workflow so that
he will remember the proper steps to use whenever you crack any software.
So step one always run a program to observe its behavior.
You should running outside of any debugger you just want to see what it does.
Maybe you ask you for a 0 number and if you enter the wrong serial number it will give you an error
message.
Or it could give you a next screen warning you.
You have 30 days trial asking you to buy a license or anything else.
So just observe the behavior first and then second you will want to look a program in the eye.
The IEEE is the type C so that you can analyze to be analyze the program executable which is also known
as the EIC file.
That way you can know what is the proper entry point for the executable and also analyzing you.
The IEEE can also tell you how the think is.
For example the pecker.
In any event I used to compress the file.
Then the third step is to look the program in the SCC for debug and after loading the program existing
for DG You will want to analyze the instructions and then try to reverse the jumps in order to avoid
showing the baton message debate message sheer could be something like wrong see your number.
Or it could be something let me ask you to buy the license for the software.
And then he will want to instead try to make any program.
Sure no good message no good message here will be something like for example correct 0 number and all
this software has been registered or something like that so you should try to analyze the gems and try
to reverse the jumps by playing if there is a f flight the zero flight and then the step four is to
search for proper instruction to patch and to assemble a new instruction to replace the all instruction.
The reason why we patch in because we want to make it permanent thus modifying the zero fly alone is
not permanent.
So that's why Step 4 is necessary and then number 5.
Once you identified the correct instruction if patch maybe you only use A B instructions no operate
no operation instructions.
All you want to jump some way.
So you need to assemble those instructions to replace the old ones after that you can best a file which
is number 5 and then load the new patch and test it and then repeat it again from 4 and 5 4 in 5.
So sometimes you may need to do step 4 and 5 repeatedly a few times until you get a bash which satisfies
your target.
That is to make the program do what you want it to do.
For example become a registered software or become a remove a next screen which gives nagging you are
in queue congratulate you on purchasing the software or whatever it might be.
So that is the summary of all the steps one to find which you always follow whenever you create any
software.
So that is all.
Thank you very much.