Showing posts with label How to find Crack of any Software. Show all posts
Showing posts with label How to find Crack of any Software. Show all posts
Friday, 7 June 2013
How To Find Crack Software In Internet
This summary is not available. Please
click here to view the post.
The Removal of Software Copy Protection
For your benefit, I have again delved into the seedy underbelly of the Internet to help keep you informed of what it has to offer.
I submit this report on Cracking for your approval.
A program successfully stripped of protections is then known as having been "Cracked".
Some of the removed protections include:
The most common belief stated online is that it is legal to write, upload and even download a Crack, as long as you don't use it to disable a software title's copy protection. However on 10-24-97, it was reported here in the U.S. that two separate arrests were made for the "illegal distribution of Cracks."
The news article reveals a few interesting points about how the FBI and the SPA had two sites under surveillance for seven months!
Wow, it took that long to gather evidence!
The article also states that the SPA found over 17,000 sites listed on the net that were similar to the ones taken down. Lets see, at seven months for every two sites that would take them only 4,958 years to bust them all.
While it may or may not be illegal to use and distribute Cracks, the legality of actually "Cracking" a piece of software is an entirely different matter.
In the United States, several court cases have ruled that the reverse engineering of software is legal, as long as the motive is not commercial gain.
Read more about cases that ruled in favor of the right to disassemble software.
You may have read the above text and said to yourself, "Hey the software license says I am forbidden to decompile the software I own."
Did that hot new software title format your hard drive? Nothing the manufacturer can do for you because you do not "own" the title and only legal owners have the right to demand compensation.
In reality of course, things are different. Even the standard "Software License" states that depending on where you live, all the previous gibberish "may not apply to you".
This does not stop them from saying it however, also you "must agree" to this license or you will not be allowed to proceed with the installment of most software titles.
The news media wasted no time in gleefully broadcasting video, graphically demonstrating just how awful burning to death in an "ugly car" could be.
I can only guess at the event that will provoke the regulation of the computer industry. For the chances of something happening are good, for history has a habit of repeating itself.
Sorry for the digresion but I just love to ramble on about all kinds of irrelevant shit.
Astalavista Look no further than this site for that crack that your too lazy to learn to write yourself.
Since the file size of most Cracks are small, around (5-10 KB), you can find them posted on Usenet, even if your provider does not carry binary newsgroups. Alt.cracks is one group that receives thousands of weekly posts.
Update: Cracks are no longer small in the age of broadband, software bloat and huge storage capacities. Usenet is not what it used to be with regards to cracks. Astalavista is your best bet.
Incredible though it may sound, there is a program called Oscar, yes the same green thingy from Sesame Street, that you can download containing well over 7,000 serial numbers. The latest version is Oscar 10.2 You can also find a lot of lists floating around the net containing thousands of serial numbers.
Update: I still have a copy of this on a old hard drive, serial #'s are between 12-15 years old now. But still fun to look through.
Many people involved in Cracking protection schemes say they are in it for the challenge, as well as, the opportunity to learn more about how programs communicate with the operating system, memory and microprocessor.
Cracking a program can be an excellent way to learn about programming since you often need to debug and/or disassemble a program. By doing these things you get to trace or step through the inner workings of the software, as well as, receive a text readout of the source code displayed in assembly language (ASM). I'll talk more about these two cracking methods a little later.
Note: ASM is the language used to write the tight, fast code needed for the graphics you see in 3D video games.
You'll find a lot of disdain among Crackers for the software companies use of reusable object code development platforms like Visual C++. They feel that these type of languages do most of the work for the programmer, who in turn, never learns how to write good code, much less an uncrackable protection scheme.
HMEMCPY can be used to "trap" valid serial numbers for shareware programs. Using a debugger such as Soft-Ice, you can set a "breakpoint" on HMEMCPY, so that the debugger pops up when HMEMCPY is called. Now that your serial number, and most likely the correct one are stored in RAM, a cracker can proceed to "fish" for a valid serial number.
Many shareware programs utilize HMEMCPY for comparisons of serial numbers, and this method is extremely effective on applications written in Delphi or Visual Basic.
The next technique involves disabling jumps and is almost certain to work, IF, you can find them.
This cracking method involves disassembling the target programs (.exe) file using either my old favorite, Wdasm 8.93, or OllyDBG which, as I stated earlier, outputs the programs source code in assembly language (ASM).
While using disassemblers in this fashion will not likely reveal the actual serial or registration number, it will expose the locations in the code where the softwares protections lurk. Once found, these protections are sometimes easily disabled, allowing for the program to be registered by entering the wrong info or no info at all.
Here is an edited view of disassembled code of a software program produced in one of the windows in OllyDBG.
The third line from the top 00484B18 shows that it contains a "Jump if Zero" instruction 74 1A (JZ) that will land at "00484B34.... 6A 30... PUSH 30" which is right on top of the line that says "Registration Error".
Replacing the "Jump if Zero" instruction to a "Jump if NOT Zero" 75 1A or two "NOP" instructions is all that's needed for this program to thank you for being a swell guy and registering it.
The program would not be permanently cracked, there are a couple of other places in the code that would need patching. Also, this is a Delphi program so there are jumps and compares all over the place, but a cracker would be on their way to cracking this program.
The Cracking groups "reputation" is at stake. Cracking is hard, tedious, dull and frustrating work. Seriously, try it sometime. See if you can last 5 minutes without wanting to blow your brains out. Some of the work these guys do borders on genius, so respect from peers is important.
One of the reasons you see so many new versions of software, especially shareware, is that the software authors also watch this group and release new versions that can withstand the previous Crack. This is not always the case as some cracks work with many versions.
The Cracks FAQ is one of the best documents on the topic of Cracks that I've ever seen. And trust me, I've seen a shit load o' documents. Packed with all kinds of helpful tips and info, it will go a long way toward answering your questions about Cracks and Cracking or Getting High on Crack.
Reading these documents will give you a whole new "perspective" on how just like cracking is the attempt to gain the hidden secrets of a software program, the same type of techniques can also be applied when trying to learn what is really going on in the world, without having to take the word of the government or news media.
Here are all twelve documents in one zip file - How to Crack (120 kb).
Fravia's (R.I.P) is a great site that discusses every aspect of Cracking. You can learn more about the tools listed below, as well as, read some of the many tutorials, pages of commentary and advice, or actually download some of the tools you'll need to get more involved in Cracking.
Even though Fravia has departed this world, his site lives on as a testament to his devotion to seeking a deeper understanding of the world around him... or just blatant socialism.
The Legend of Random blog is a virtual treasure chest of useful tools, tutorials and some of the best links I've come across.
The Art of Assembly The most complete ASM tutorial on the net. Strongly recommended.
I submit this report on Cracking for your approval.
A Definition
Cracking is defined as the attempt to remove the copy protections inserted into software programs. A program successfully stripped of protections is then known as having been "Cracked".
Some of the removed protections include:
Time limits - example of this is a 30-day trial period, after which the program will no longer run.
Nag Screen - graphic that appears, at programmer determined intervals, asking you to register the software.
Serial Number - the use of an assigned number that is required for the program to function.A Crack usually comes in the form of an .exe or .com file. Like a file you download from a software company to correct a bug or add a feature, a Crack patches one or more of the applications .dll files or the main .exe file itself.
Is This Legal?
Similar to the other Internet giveaway, Warez, the legality of Cracks is far from being globally defined.The most common belief stated online is that it is legal to write, upload and even download a Crack, as long as you don't use it to disable a software title's copy protection. However on 10-24-97, it was reported here in the U.S. that two separate arrests were made for the "illegal distribution of Cracks."
The news article reveals a few interesting points about how the FBI and the SPA had two sites under surveillance for seven months!
Wow, it took that long to gather evidence!
The article also states that the SPA found over 17,000 sites listed on the net that were similar to the ones taken down. Lets see, at seven months for every two sites that would take them only 4,958 years to bust them all.
While it may or may not be illegal to use and distribute Cracks, the legality of actually "Cracking" a piece of software is an entirely different matter.
Software License
The legality of reverse engineering
software has been established in many parts of the world. In Europe
for example, this activity is clearly defined as legal in the European Union Directive.In the United States, several court cases have ruled that the reverse engineering of software is legal, as long as the motive is not commercial gain.
Read more about cases that ruled in favor of the right to disassemble software.
You may have read the above text and said to yourself, "Hey the software license says I am forbidden to decompile the software I own."
You're right, it does. Except, you don't "own it". You are being "allowed to license it".The reason for this is so that the company that produced the software can be exempt from any liability resulting from a faulty product.
Did that hot new software title format your hard drive? Nothing the manufacturer can do for you because you do not "own" the title and only legal owners have the right to demand compensation.
In reality of course, things are different. Even the standard "Software License" states that depending on where you live, all the previous gibberish "may not apply to you".
This does not stop them from saying it however, also you "must agree" to this license or you will not be allowed to proceed with the installment of most software titles.
Fish Tales and Hand Grenades
The computer industry is no corporate
slouch when it comes to "telling lies" to deceive the public. Here are
just a few examples:- 17" Monitor? - Not even 16", if you're lucky 15.9" - I guess they thought the average computer user would not notice the difference in an item that they only stare at all day!
- 56k x2 Modem? - Sorry, maxes out at 53k recv. and 33.6k sending. USRobotics blames this on FCC regulations, actually the problem is the modem sends too much voltage thru the phone line, limiting speed to 53k. But hey, what's one more lie among friends?
- 32x CD-rom? - Possibly the greatest flat out, screw you, lie yet - These drives average speeds of between 16X - 20X and are only able to achieve a rate as high as 30X. The 30X speed is only attained when the CD has data written all the way to the edges of the disk. Once the outer edge data is read the CD drive slows to half speed. This is why you see CD-ROM Drives labeled as 24/12 or 32/16.
Note: The mere sight of a gremlin caused other drivers to veer off the side of roads in utter fear of these "moon buggies".But it was the pinto's bad habit of exploding like a hand grenade, that finally brought the auto industry back down to earth. The pinto was as ugly as it was dangerous, which made for great T.V.
The news media wasted no time in gleefully broadcasting video, graphically demonstrating just how awful burning to death in an "ugly car" could be.
I can only guess at the event that will provoke the regulation of the computer industry. For the chances of something happening are good, for history has a habit of repeating itself.
Sorry for the digresion but I just love to ramble on about all kinds of irrelevant shit.
Where to Search
As I state in my article on Warez,
you should be able to track down all the info you need regarding this
subject by making good use of the many search engines the net has to
offer.Astalavista Look no further than this site for that crack that your too lazy to learn to write yourself.
Since the file size of most Cracks are small, around (5-10 KB), you can find them posted on Usenet, even if your provider does not carry binary newsgroups. Alt.cracks is one group that receives thousands of weekly posts.
Update: Cracks are no longer small in the age of broadband, software bloat and huge storage capacities. Usenet is not what it used to be with regards to cracks. Astalavista is your best bet.
Incredible though it may sound, there is a program called Oscar, yes the same green thingy from Sesame Street, that you can download containing well over 7,000 serial numbers. The latest version is Oscar 10.2 You can also find a lot of lists floating around the net containing thousands of serial numbers.
Update: I still have a copy of this on a old hard drive, serial #'s are between 12-15 years old now. But still fun to look through.
A Deeper Understanding
You can find sites online run by would be "Capitalists"
who download as many Cracks as they can find and then offer to sell to
you for a price. Avoid these places, most of the people who Crack these
programs are more than glad to give them away for they are said to be in
it for a "deeper understanding."Many people involved in Cracking protection schemes say they are in it for the challenge, as well as, the opportunity to learn more about how programs communicate with the operating system, memory and microprocessor.
Cracking a program can be an excellent way to learn about programming since you often need to debug and/or disassemble a program. By doing these things you get to trace or step through the inner workings of the software, as well as, receive a text readout of the source code displayed in assembly language (ASM). I'll talk more about these two cracking methods a little later.
Note: ASM is the language used to write the tight, fast code needed for the graphics you see in 3D video games.
You'll find a lot of disdain among Crackers for the software companies use of reusable object code development platforms like Visual C++. They feel that these type of languages do most of the work for the programmer, who in turn, never learns how to write good code, much less an uncrackable protection scheme.
Cracking the Code
There are many different ways to penetrate most software programs protections. I will briefly focus on two of them.HMEMCPY can be used to "trap" valid serial numbers for shareware programs. Using a debugger such as Soft-Ice, you can set a "breakpoint" on HMEMCPY, so that the debugger pops up when HMEMCPY is called. Now that your serial number, and most likely the correct one are stored in RAM, a cracker can proceed to "fish" for a valid serial number.
Many shareware programs utilize HMEMCPY for comparisons of serial numbers, and this method is extremely effective on applications written in Delphi or Visual Basic.
The next technique involves disabling jumps and is almost certain to work, IF, you can find them.
This cracking method involves disassembling the target programs (.exe) file using either my old favorite, Wdasm 8.93, or OllyDBG which, as I stated earlier, outputs the programs source code in assembly language (ASM).
While using disassemblers in this fashion will not likely reveal the actual serial or registration number, it will expose the locations in the code where the softwares protections lurk. Once found, these protections are sometimes easily disabled, allowing for the program to be registered by entering the wrong info or no info at all.
Here is an edited view of disassembled code of a software program produced in one of the windows in OllyDBG.
00484B11 .... |. E8 A240FDFF..... CALL ####32.00458BB8
00484B16 .... |. 84C0 ........... TEST AL,AL
00484B18 .... |. 74 1A .......... JZ SHORT ####32.00484B34
00484B1A .... |. 6A 00........... PUSH 0 .......................... ; /Arg1 = 0
00484B1C .... |. B9 6C4B4800..... MOV ECX,####32.00484B6C ........ ; |ASCII "Shareware Registration"
00484B21 .... |. BA 844B4800..... MOV EDX,####32.00484B84 ........ ; |ASCII "Thanks for registering, You are Swell, really, I mean it!"
00484B32 .... |. EB 18........... JMP SHORT ####32.00484B4C
00484B34 .... |> 6A 30 .......... PUSH 30
......................... ; /Arg1 = 30
00484B36 .... |. B9 9C4B4800..... MOV ECX,####32.00484B9C ....... ; |ASCII "Registration Error"
00484B3B .... |. BA B04B4800..... MOV EDX,####32.00484BB0 ....... ; |ASCII "Invalid name or registration number."
00484B4C .... |> 33C0 ........... XOR EAX,EAX
The third line from the top 00484B18 shows that it contains a "Jump if Zero" instruction 74 1A (JZ) that will land at "00484B34.... 6A 30... PUSH 30" which is right on top of the line that says "Registration Error".
Replacing the "Jump if Zero" instruction to a "Jump if NOT Zero" 75 1A or two "NOP" instructions is all that's needed for this program to thank you for being a swell guy and registering it.
The program would not be permanently cracked, there are a couple of other places in the code that would need patching. Also, this is a Delphi program so there are jumps and compares all over the place, but a cracker would be on their way to cracking this program.
Do Cracks Really Work?
In a word, HELL YEAH they do. Oh, that's two words. But the fact remains, Cracks do indeed work.The Cracking groups "reputation" is at stake. Cracking is hard, tedious, dull and frustrating work. Seriously, try it sometime. See if you can last 5 minutes without wanting to blow your brains out. Some of the work these guys do borders on genius, so respect from peers is important.
One of the reasons you see so many new versions of software, especially shareware, is that the software authors also watch this group and release new versions that can withstand the previous Crack. This is not always the case as some cracks work with many versions.
The Cracks FAQ is one of the best documents on the topic of Cracks that I've ever seen. And trust me, I've seen a shit load o' documents. Packed with all kinds of helpful tips and info, it will go a long way toward answering your questions about Cracks and Cracking or Getting High on Crack.
Cracking - Learning from the Masters
Long did I search for info on the art of cracking. Just when I thought it only to be a myth, I stumbled onto one out of a total of a dozen
"lessons" written by +ORC.Reading these documents will give you a whole new "perspective" on how just like cracking is the attempt to gain the hidden secrets of a software program, the same type of techniques can also be applied when trying to learn what is really going on in the world, without having to take the word of the government or news media.
Here are all twelve documents in one zip file - How to Crack (120 kb).
Fravia's (R.I.P) is a great site that discusses every aspect of Cracking. You can learn more about the tools listed below, as well as, read some of the many tutorials, pages of commentary and advice, or actually download some of the tools you'll need to get more involved in Cracking.
Even though Fravia has departed this world, his site lives on as a testament to his devotion to seeking a deeper understanding of the world around him... or just blatant socialism.
The Legend of Random blog is a virtual treasure chest of useful tools, tutorials and some of the best links I've come across.
The Art of Assembly The most complete ASM tutorial on the net. Strongly recommended.
Tools of the Trade
Here is a list of some of the tools used in Cracking: For a full list, check out Random's blog that I linked above. He has them all. I would stop by soon, seeing that like Mammon and +Fravia before him, Random has seemingly vanished. I do hope everything is ok, very informative website.Wdasm 8.93 - old, but proud, this shareware disassembler also includes a debugger.
Soft-Ice - the most awesome cracking tool back in the day, from Numega.
OllyDBG - Olly Debugger is pronounced Ollydebug and always spelled OllyDBG, has taken over as the most indispensable tool in Cracking. You can get it here.
Hacker Viewer (hiew.exe) - used to patch disassembled code.
WinHex 17.0 - This program provides a rich set of functional capabilities. This program can be found here.
Text Editor - get one that is made with programmers in mind. Ultra Edit (my favorite) or even the one I'm using to type this, Notepad ++. Every possible feature for the very reasonable price of free.
How to Use Windows 7 Without Activation
Most of you might be aware of the fact
that it is possible to use Windows 7 and Vista for 120 days without
activation. This is actually possible using the slmgr -rearm command which will extend the grace period from 30 days to 120 days.
However, in this post I will show you a small trick using which it is possible to use Windows 7 without activation for approximately an year! Here is a way to do that.
Step-1: Go to “Start Menu -> All Programs -> Accessories“.
Right click on the “Command Prompt” and select “Run as Administrator“. If you are not the administrator, then you are prompted to enter the password, or else you can proceed to step-2.
Step-2: Now type the following command and hit Enter:
slmgr -rearm
Step-3: You will be
prompted to restart the computer. Once restarted, the trial period will
once again be reset to 30 days. You can use the above command for up to 3
times by which you can extend the trial period to 120 days without
activation.
Step-4: Now comes the actual trick by which you can extend the trial period for another 240 days. To do this, open the Registry Editor (type regedit in “Run” and hit Enter) and navigate to the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform
Step-5: In the right-side pane, change value of SkipRearm to 1.
Step-6: Now, you should be able to use the slmgr -rearm command for another 8 times so that you can skip the activation process for another 240 days. So you will get 120 + 240 = 360 days of free Windows 7 usage.
120 days using “slmgr -rearm” command before registry edit
+
240 days using “slmgr -rearm” command after registry edit
= 360 Days
+
240 days using “slmgr -rearm” command after registry edit
= 360 Days
I hope you like this post. Please pass your comments…
Hack Software and Run the Trial Program Forever
However, there is a way to run the software programs so that they function beyond the trial period. Isn’t this interesting?
Well, before I tell you how to hack the
software and make it run in the trial mode forever, we will have to
first understand how the licensing scheme of these programs work. I’ll
try to explain this in brief.
When the software programs are installed
for the first time, they make an entry into the Windows Registry with
the details such as Installed Date and Time, installed
path etc. After the installation, every time you run the program, it
compares the current system date and time with the installed date and
time. With this, it can make out whether the trial period is expired or
not.
So, with this being the case, just
manually changing the system date to an earlier date will not solve the
problem. For this purpose there is a small tool known as RunAsDate.
RunAsDate is a small utility that allows
you to run a program in the date and time that you specify. This
utility doesn’t change the current system date, but it only injects the
date/time that you specify into the desired application.
RunAsDate intercepts the kernel API
calls that returns the current date and time (GetSystemTime,
GetLocalTime, GetSystemTimeAsFileTime), and replaces the current
date/time with the date/time that you specify. It works with Windows
2000, XP, 2003, Vista and 7.
You can download RunAsDate from the following link:
Steps to Hack the Software and Run the Trial Program Forever:
You will have to follow these tips carefully to successfully hack a software and make it run in the trial mode forever:
-
Note down the date and time, when you install the software for the first time.
-
Once the trial period expires, you must always run the software using RunAsDate.
-
After the trial period is expired, do not run the software(program) directly. If you run the software directly even once, this hack may no longer work.
-
It is better and safe to inject the date of the last day in the trial period.
For example, if the trial period expires on jan 30 2009, always inject the date as jan 29 2009 in the RunAsDate. I hope this helps! Please express your experience and opinions through comments.
Thursday, 6 June 2013
How To Crack a File
I did not write this myself but i found it extremely useful. Enjoy it
PART 1:
0. Introducion:
I have read many cracking tutorials lately. Frankly speaking, I myself learned cracking from tutorials (and some book, but this doesnt really matter). The majority of the cracking tutorials out there have a few disadvantages: either they are too long and contain a lot of garbage, or they are too short, and don't contain the basics.
I decided to write a tutorial which will not have those two disadvantaged.
Anyway, I divided the tutorial into 3 parts:
Part 1: Introduction, tools and The basics of cracking.
Part 2: Practical training, using W32Dasm, and HIEW
Part 3: Key-generators.
Welcome to the first part. ;-)
1. Disclaimer:
I created this tutorial for informational purposes only!
Much of the information in this document can be used to perform illegal activities!
Don't attempt to do anything stated in this document!
If you do attempt to do anything, you are solely and fully responsible for what you do!
If you get caught and get in any kind of trouble, it's your own fault!
If you intend to use this information to impress your friends, leave it and grow up!
If you don't agree to this, do not read any more!
If you crack a program, and either sell the crack or offer it for free, it is a crime!
2. What is Cracking?
For me, cracking is:
"Letting a program, which is on your computer behave as you want it to behave and not behave as someone else (the programmer) wants"
As INTERN said:
"Hey, it is your stuff right? your numbers, your bits, you should be able to do anything you wish to do with it
"
Actually, I agree to this.
So cracking is modifying your programs, and making them work they way you want them to. U can get a free demo program, crack it, and use it. BUT!!!! I repeat, if you crack a program, and start selling the cracked version or even offering it for free, it is a crime!
After reading those three tutorials (this is the first one in thsi series), you will feel the power you have in your hands (I mean, in your head).
well, let's get started?
3. Tools
There are very few tools you need by now...
It is very easy to find them over the web, cause they are quite popular:
The first one is "Win32 Disassembler", which is also know ans W32Dasm.
The Win32 Disassembler allows you to:
Disassemble files - translate the program to it's assembly origin, or machine code.
The file types which can be disassambled in Win32 Disassembler:
exe, 386, com, cpl, drv, dll, fon, mpd, ocx, vbx, vbx and sys.
Load the program proccess and trace the program.
Browse the disassembled file and go to any code location that you want.
Find text.
Execute, insert or remove jumps and calls.
Import and export functions.
Show a HEX display of a code area.
Show the list of the STRINGS, DIALOGS and REFERENCES.
Save the Disassembly source in text format.
Well, u can get it in almost any cracking site, but I'll give you some URLs:
http://wowsites.com/meiner/w32dsm89.zip
I think that's about enough. If any of these links goes down, please alert me.
The second tool you need is Hiew, which is also known as Hacker's View. The Hacker's View Tool allowes you to:
Disassemble files.
Make changes in the disassembled file, such as:
write commands, modify commands and reassemble the file.
View the file in ASCII, Hex or assembly mode.
You can also download an excellent program for cracking called Soft-ICe. Anyway, we won't need it in this part of the tutorial. Anyway, here are some URLs for Soft-ICe.
Please use the (Astalavista.com) search engines to find this programs!
4. The Main steps of cracking
There are 7 steps in the process of cracking:
Run the program you want to crack and learn it's standard behavior. Try to locate strings and keywords, try to enter the password and see how the program responds.
Open up the program with the W32Dasm and disassamble it.
Find typical and common strings in the disassembly that appeared in the program. In most cases, you have to look for keywords such as: password, name, date, expired, time limit, wrong, entered and so on.
Find and observe the password generator, find the learn protection routine and the API calls.
Try to understand the jumping mechanism of the protection.
Open up the program in HIEW. Change the jump of the flow control to it's oposite jump command, or nop it out.
Run and see how the change you have made in the original program affected it. Feel the power you have, the power of cracking, letting programs behave as you want them to.
Learn those steps very well, until u dream of them, u will use them in every program you crack.
5. Basic terms in Assembly
A. Registers:
Registers are variables which are stored in your processor. The processor uses these variables for basic mathimatical and logical operations. The mostly used registers are: eax, ebx, ecx and edx. Sometimes you will see edi, esi, esp, ebp. There are three types of registers: 32Bit registers, 16Bit registers and 8Bit registers. The 32Bit registers start with e, such as eax. There are 16Bit equivalents of these registers. The only Difference between the two types is the veriable size. These registers are: ax, bx, cx, dx, di, si, sp, bp. There are also 8 bit registers. Tthe 8Bit registers are: al, ah, bl, bh, cl, ch, dl, dh. l - means the lower 8 bits of the 16Bit register. h - means the higher 8 bits of the 16Bit register. Here the l stands for the lower and h for the higher 8 bits of a 16 bit register.
B. Flags:
Flags are Boolean variables (get 0 or 1 values). Flags are used by the processor for internal logical and mathimatical operations, in order to get the result of the operation. The most important flag is the Zero Flag, which can get zero or non-zero (1) values.
C. Code Flow
When you are analyzing a piece of code, you must understand that the processor is actually quite stupid, and all it does is to simply follow the basic instructions, line by line. It does anything the code tells it to do, and cannot do anything that is not written in the code (unless it has been run over by a herd of cows and abducted by aliens). This is why you have to think like the processor when you're analyzing a piece of code, and to act like it (just don't get used to it! Inhale, exhale, inhale, exhale... nevermind, stupid joke)
You have to do everything the processor does, you have to compare
registers and variables, execute jumps and calls, calculate Basic
mathimatical operations, store and load register values and adresses,
and so on... The processor has an instruction pointer especially for
this, which is also called IP (it has nothing to do with IP addresses in
the Internet Protocol, trust me). Using the instruction pointer, the
processor points to the instruction that is about to be executed. The
processor also has and executes instructions which change the code flow.
These instructions can be function calls, any other routine calls, jumps, conditional jumps, which depend on the zero flag, negative conditional jumps...
6. Conclusion
In this part of the tutorial we have learnt the meaning of the word cracking. Making programs behave as you want them to, and not the way the programmer wants them to. We have also learnt about the basic and the popular tools of cracking: W32Dasm, Hiew and SoftICE. And finally we have learnt the 7 main steps of cracking.
Now, Before you go to the next chapter, you have to learn these 7 steps and download the tools mentioned above, because we can't go on to the next chapter unless you have those tools and know the steps.
PART 2:
0. Introduction:
In this part, the second part of the cracking tutorial, you will learn to use the most important tools of the common cracker: W32Dasm and HIEW. You will also learn to crack some simple programs.
The tutorials are divided into 3 parts:
Part 1: Introduction, tools and the basics of cracking.
Part 2: Practical training, using W32Dasm, and HIEW.
Part 3: key-generators.
Welcome to the second part. :-)
1. Disclaimer:
I created this tutorial for informational purposes only!
Much of the information in this document can be used to perform illegal activities!
Don't attempt to do anything stated in this document!
If you do attempt to do anything, you are solely and fully responsible for what you do!
If you get caught and get in any kind of trouble, it's your own fault!
If you intend to use this information to impress your friends, leave it and grow up!
If you don't agree to this, do not read any more!
If you crack a program, and either sell the crack or offer it for free, it is a crime!
2. The main steps of cracking
You have already seen these steps in the previous part of the tutorial, but it's very important to know them. Remembering these steps and following them is 40% of the way towards success in cracking the program!!!
There are 7 steps in the cracking process:
Run the program you want to crack and study it's behavior. try to locate strings and keywords, try to enter the password and see how the program responds.
Open the program with the W32Dasm and disassemble it.
Find typical and common Strings in the disassembly that appeared within the program.
in most cases, you have to look for keywords such as: password, name, date, expired,
Time limit, wrong, entered and so on.
Find and observe the password generator, find the learn protection routine and the API calls.
Try to understand the jumping mechanism of the protection.
Open the program in Hiew. change the jump of the flow control to it's opposite jump command, or NOP it out.
Run and check how the change you have made in the original program affected it.
Feel the power you have, the power of of cracking, making programs behave the way you want them to.
Learn those steps very well, until u dream of them, u will use them in every program you crack.
3. Additional programs you need to have for this part of the tutorial
By now, in this part of the tutorial, you have learnt the main steps of cracking. Now, you are going to crack your first program.
But before that, you need to get a little program called: "Sweet Little Piano" You can download it from: http://www.ronimusic.com/
Now, when you have the program, let's start!
4. Cracking the first program (Sweet little Piano)
Now we will follow each step and crack the program:
Step 1: Running the program:
Well, Run it! Duh... :-)
Well, what do we see here..... The program opens two text files. Also we see "Unregistered Shareware" on the caption bar... Now let's open the Help menu for any registration options... Humm, what do we see here now...
oh, it's a password option... Well, select it and enter something (don't hope it will be right :-)). To see what happens... Click OK.. Hmm, nothing happens.... Maybe it accepted it? Hmm.. no way... the caption bar still says Unregistered... Ok close it... bah ... more text files ... and a notification that the settings are not saved in the unregistered version ... well ... kind of irritating those text files! Let's fix it :-)
Step 2: Disassemble the program:
Disassemble the program. Good, small is fast :-) Always.... Now, we don't have any strings that pop up when we want to register something... Let's browse for strings like registered, unregistered, the string about the unsaved settings. Hmm... evaluation time left ... password.txt.... passworddialog.... sweet little piano - Unregistered <<-- looks like our caption bar ;-) go on...Thanks for registering ... cool! So it thanks you anyway :-) Let's jump to that place ... Double click on it an we will pop right on top of the registration routine...
Step 3: Analyzing the protection routine.... / Understanding the jumping Mechanism...
Let's analyze the protection routine.
////////////////////// Code snip ///////////////////////////
ADDRESS MACHINE CODE ASSEMBLER INSTRUCTIONS
* Possible Reference to Dialog: PASSWORDDIALOG, CONTROL_ID:0064, ""
|
:00401715 6A64 push 00000064
:00401717 53 push ebx
* Reference To: USER32.GetDlgItemTextA, Ord:0000h
|
:00401718 E8A5B50000 Call 0040CCC2
:0040171D E822FFFFFF call 00401644
:00401722 85C0 test eax, eax
:00401724 741E je 00401744
:00401726 6A30 push 00000030
* Possible StringData Ref from Data Obj ->"SweetPiano"
|
:00401728 6866D24000 push 0040D266
* Possible StringData Ref from Data Obj ->"Thanks for registering!"
|
:0040172D 68FED14000 push 0040D1FE
:00401732 53 push ebx
////////////////////// Code snip ///////////////////////////
PasswordDialog ... a call to GetDlgItemTextA ... another call.... a test... and depending on the test a je.... The je jumps over the thank you ... And just ends the dialog box ... without telling you that you entered something wrong... So this is right ... we did indeed not see that we typed something wrong ... but apparently we are supposed to see if we type something right :-)
Again execute the je jump, and look where it goes to ... return from the jump.... Now lets try to rewrite what goes on here...
call ShowPasswordDialog
call GetEnteredText
call IsEnteredTextGood
test value in eax
je QuietExit
ShowThanksForRegistering
QuietExit:
the source code must have looked like this :
GetDlgItemText(_ID_Serial);
if (EnteredTextGood) ShowThanksForRegistering
// else nothing....
This is another interesting piece of code.... test eax, eax ... this assembler instruction tests if the value of eax is equal to itself ... if it is it is equal ... so a je instruction jumps ... if it is not equal, it does not jump.... To crack this program we can change the je instruction into two nop instructions... and we are done...
We have seen here, that the call has put a value in eax.... something which is not equal to zero or a zero... In our previous example we saw that the called Is_Serial_Valid call set some value in memory ... Here we see that the called Is_Serial_Valid call sets the eax register of our processor to some value....
Step 4: Changing the original program...
So modify it :-)
Open Hiew.
Open the file within Hiew.
Find the Adress of the line in W32Dasm (it's on the status bar beginning with '@').
Press F5 in Hiew.
Enter the address you have found in (4) and press ENTER.
Press F3 - for activating the write option.
Press F2 - to change the instruction.
Replace the command by 'NOP' (without quotes), which means NO OPERATION.
Now a new command appeared in the next line.
Replace it by NOP too.
If another new instruction hasn't appeared, Press F9 to update the file.
Press F10 to exit.
Run the program and see the result.
If you didn't succeed, have any questions or need any additional information, E-Mail me and I will answer all of your questions.
5. Conclusion
I gave this quite 'hard' cracking example so that u know that if you crack this program, you can crack almost every program, and most of them are much simpler to crack. In the next part you will learn to detect key generators and crack them.
Before you go to the next chapter, go over the steps again, and also go over the protection mechanism detection and modification.
This tutorial was written by Tech Lord <http://blacksun.box.sk>
-Spyda
PART 1:
0. Introducion:
I have read many cracking tutorials lately. Frankly speaking, I myself learned cracking from tutorials (and some book, but this doesnt really matter). The majority of the cracking tutorials out there have a few disadvantages: either they are too long and contain a lot of garbage, or they are too short, and don't contain the basics.
I decided to write a tutorial which will not have those two disadvantaged.
Anyway, I divided the tutorial into 3 parts:
Part 1: Introduction, tools and The basics of cracking.
Part 2: Practical training, using W32Dasm, and HIEW
Part 3: Key-generators.
Welcome to the first part. ;-)
1. Disclaimer:
I created this tutorial for informational purposes only!
Much of the information in this document can be used to perform illegal activities!
Don't attempt to do anything stated in this document!
If you do attempt to do anything, you are solely and fully responsible for what you do!
If you get caught and get in any kind of trouble, it's your own fault!
If you intend to use this information to impress your friends, leave it and grow up!
If you don't agree to this, do not read any more!
If you crack a program, and either sell the crack or offer it for free, it is a crime!
2. What is Cracking?
For me, cracking is:
"Letting a program, which is on your computer behave as you want it to behave and not behave as someone else (the programmer) wants"
As INTERN said:
"Hey, it is your stuff right? your numbers, your bits, you should be able to do anything you wish to do with it
Actually, I agree to this.
So cracking is modifying your programs, and making them work they way you want them to. U can get a free demo program, crack it, and use it. BUT!!!! I repeat, if you crack a program, and start selling the cracked version or even offering it for free, it is a crime!
After reading those three tutorials (this is the first one in thsi series), you will feel the power you have in your hands (I mean, in your head).
well, let's get started?
3. Tools
There are very few tools you need by now...
It is very easy to find them over the web, cause they are quite popular:
The first one is "Win32 Disassembler", which is also know ans W32Dasm.
The Win32 Disassembler allows you to:
Disassemble files - translate the program to it's assembly origin, or machine code.
The file types which can be disassambled in Win32 Disassembler:
exe, 386, com, cpl, drv, dll, fon, mpd, ocx, vbx, vbx and sys.
Load the program proccess and trace the program.
Browse the disassembled file and go to any code location that you want.
Find text.
Execute, insert or remove jumps and calls.
Import and export functions.
Show a HEX display of a code area.
Show the list of the STRINGS, DIALOGS and REFERENCES.
Save the Disassembly source in text format.
Well, u can get it in almost any cracking site, but I'll give you some URLs:
http://wowsites.com/meiner/w32dsm89.zip
I think that's about enough. If any of these links goes down, please alert me.
The second tool you need is Hiew, which is also known as Hacker's View. The Hacker's View Tool allowes you to:
Disassemble files.
Make changes in the disassembled file, such as:
write commands, modify commands and reassemble the file.
View the file in ASCII, Hex or assembly mode.
You can also download an excellent program for cracking called Soft-ICe. Anyway, we won't need it in this part of the tutorial. Anyway, here are some URLs for Soft-ICe.
Please use the (Astalavista.com) search engines to find this programs!
4. The Main steps of cracking
There are 7 steps in the process of cracking:
Run the program you want to crack and learn it's standard behavior. Try to locate strings and keywords, try to enter the password and see how the program responds.
Open up the program with the W32Dasm and disassamble it.
Find typical and common strings in the disassembly that appeared in the program. In most cases, you have to look for keywords such as: password, name, date, expired, time limit, wrong, entered and so on.
Find and observe the password generator, find the learn protection routine and the API calls.
Try to understand the jumping mechanism of the protection.
Open up the program in HIEW. Change the jump of the flow control to it's oposite jump command, or nop it out.
Run and see how the change you have made in the original program affected it. Feel the power you have, the power of cracking, letting programs behave as you want them to.
Learn those steps very well, until u dream of them, u will use them in every program you crack.
5. Basic terms in Assembly
A. Registers:
Registers are variables which are stored in your processor. The processor uses these variables for basic mathimatical and logical operations. The mostly used registers are: eax, ebx, ecx and edx. Sometimes you will see edi, esi, esp, ebp. There are three types of registers: 32Bit registers, 16Bit registers and 8Bit registers. The 32Bit registers start with e, such as eax. There are 16Bit equivalents of these registers. The only Difference between the two types is the veriable size. These registers are: ax, bx, cx, dx, di, si, sp, bp. There are also 8 bit registers. Tthe 8Bit registers are: al, ah, bl, bh, cl, ch, dl, dh. l - means the lower 8 bits of the 16Bit register. h - means the higher 8 bits of the 16Bit register. Here the l stands for the lower and h for the higher 8 bits of a 16 bit register.
B. Flags:
Flags are Boolean variables (get 0 or 1 values). Flags are used by the processor for internal logical and mathimatical operations, in order to get the result of the operation. The most important flag is the Zero Flag, which can get zero or non-zero (1) values.
C. Code Flow
When you are analyzing a piece of code, you must understand that the processor is actually quite stupid, and all it does is to simply follow the basic instructions, line by line. It does anything the code tells it to do, and cannot do anything that is not written in the code (unless it has been run over by a herd of cows and abducted by aliens). This is why you have to think like the processor when you're analyzing a piece of code, and to act like it (just don't get used to it! Inhale, exhale, inhale, exhale... nevermind, stupid joke)
These instructions can be function calls, any other routine calls, jumps, conditional jumps, which depend on the zero flag, negative conditional jumps...
6. Conclusion
In this part of the tutorial we have learnt the meaning of the word cracking. Making programs behave as you want them to, and not the way the programmer wants them to. We have also learnt about the basic and the popular tools of cracking: W32Dasm, Hiew and SoftICE. And finally we have learnt the 7 main steps of cracking.
Now, Before you go to the next chapter, you have to learn these 7 steps and download the tools mentioned above, because we can't go on to the next chapter unless you have those tools and know the steps.
PART 2:
0. Introduction:
In this part, the second part of the cracking tutorial, you will learn to use the most important tools of the common cracker: W32Dasm and HIEW. You will also learn to crack some simple programs.
The tutorials are divided into 3 parts:
Part 1: Introduction, tools and the basics of cracking.
Part 2: Practical training, using W32Dasm, and HIEW.
Part 3: key-generators.
Welcome to the second part. :-)
1. Disclaimer:
I created this tutorial for informational purposes only!
Much of the information in this document can be used to perform illegal activities!
Don't attempt to do anything stated in this document!
If you do attempt to do anything, you are solely and fully responsible for what you do!
If you get caught and get in any kind of trouble, it's your own fault!
If you intend to use this information to impress your friends, leave it and grow up!
If you don't agree to this, do not read any more!
If you crack a program, and either sell the crack or offer it for free, it is a crime!
2. The main steps of cracking
You have already seen these steps in the previous part of the tutorial, but it's very important to know them. Remembering these steps and following them is 40% of the way towards success in cracking the program!!!
There are 7 steps in the cracking process:
Run the program you want to crack and study it's behavior. try to locate strings and keywords, try to enter the password and see how the program responds.
Open the program with the W32Dasm and disassemble it.
Find typical and common Strings in the disassembly that appeared within the program.
in most cases, you have to look for keywords such as: password, name, date, expired,
Time limit, wrong, entered and so on.
Find and observe the password generator, find the learn protection routine and the API calls.
Try to understand the jumping mechanism of the protection.
Open the program in Hiew. change the jump of the flow control to it's opposite jump command, or NOP it out.
Run and check how the change you have made in the original program affected it.
Feel the power you have, the power of of cracking, making programs behave the way you want them to.
Learn those steps very well, until u dream of them, u will use them in every program you crack.
3. Additional programs you need to have for this part of the tutorial
By now, in this part of the tutorial, you have learnt the main steps of cracking. Now, you are going to crack your first program.
But before that, you need to get a little program called: "Sweet Little Piano" You can download it from: http://www.ronimusic.com/
Now, when you have the program, let's start!
4. Cracking the first program (Sweet little Piano)
Now we will follow each step and crack the program:
Step 1: Running the program:
Well, Run it! Duh... :-)
Well, what do we see here..... The program opens two text files. Also we see "Unregistered Shareware" on the caption bar... Now let's open the Help menu for any registration options... Humm, what do we see here now...
oh, it's a password option... Well, select it and enter something (don't hope it will be right :-)). To see what happens... Click OK.. Hmm, nothing happens.... Maybe it accepted it? Hmm.. no way... the caption bar still says Unregistered... Ok close it... bah ... more text files ... and a notification that the settings are not saved in the unregistered version ... well ... kind of irritating those text files! Let's fix it :-)
Step 2: Disassemble the program:
Disassemble the program. Good, small is fast :-) Always.... Now, we don't have any strings that pop up when we want to register something... Let's browse for strings like registered, unregistered, the string about the unsaved settings. Hmm... evaluation time left ... password.txt.... passworddialog.... sweet little piano - Unregistered <<-- looks like our caption bar ;-) go on...Thanks for registering ... cool! So it thanks you anyway :-) Let's jump to that place ... Double click on it an we will pop right on top of the registration routine...
Step 3: Analyzing the protection routine.... / Understanding the jumping Mechanism...
Let's analyze the protection routine.
////////////////////// Code snip ///////////////////////////
ADDRESS MACHINE CODE ASSEMBLER INSTRUCTIONS
* Possible Reference to Dialog: PASSWORDDIALOG, CONTROL_ID:0064, ""
|
:00401715 6A64 push 00000064
:00401717 53 push ebx
* Reference To: USER32.GetDlgItemTextA, Ord:0000h
|
:00401718 E8A5B50000 Call 0040CCC2
:0040171D E822FFFFFF call 00401644
:00401722 85C0 test eax, eax
:00401724 741E je 00401744
:00401726 6A30 push 00000030
* Possible StringData Ref from Data Obj ->"SweetPiano"
|
:00401728 6866D24000 push 0040D266
* Possible StringData Ref from Data Obj ->"Thanks for registering!"
|
:0040172D 68FED14000 push 0040D1FE
:00401732 53 push ebx
////////////////////// Code snip ///////////////////////////
PasswordDialog ... a call to GetDlgItemTextA ... another call.... a test... and depending on the test a je.... The je jumps over the thank you ... And just ends the dialog box ... without telling you that you entered something wrong... So this is right ... we did indeed not see that we typed something wrong ... but apparently we are supposed to see if we type something right :-)
Again execute the je jump, and look where it goes to ... return from the jump.... Now lets try to rewrite what goes on here...
call ShowPasswordDialog
call GetEnteredText
call IsEnteredTextGood
test value in eax
je QuietExit
ShowThanksForRegistering
QuietExit:
the source code must have looked like this :
GetDlgItemText(_ID_Serial);
if (EnteredTextGood) ShowThanksForRegistering
// else nothing....
This is another interesting piece of code.... test eax, eax ... this assembler instruction tests if the value of eax is equal to itself ... if it is it is equal ... so a je instruction jumps ... if it is not equal, it does not jump.... To crack this program we can change the je instruction into two nop instructions... and we are done...
We have seen here, that the call has put a value in eax.... something which is not equal to zero or a zero... In our previous example we saw that the called Is_Serial_Valid call set some value in memory ... Here we see that the called Is_Serial_Valid call sets the eax register of our processor to some value....
Step 4: Changing the original program...
So modify it :-)
Open Hiew.
Open the file within Hiew.
Find the Adress of the line in W32Dasm (it's on the status bar beginning with '@').
Press F5 in Hiew.
Enter the address you have found in (4) and press ENTER.
Press F3 - for activating the write option.
Press F2 - to change the instruction.
Replace the command by 'NOP' (without quotes), which means NO OPERATION.
Now a new command appeared in the next line.
Replace it by NOP too.
If another new instruction hasn't appeared, Press F9 to update the file.
Press F10 to exit.
Run the program and see the result.
If you didn't succeed, have any questions or need any additional information, E-Mail me and I will answer all of your questions.
5. Conclusion
I gave this quite 'hard' cracking example so that u know that if you crack this program, you can crack almost every program, and most of them are much simpler to crack. In the next part you will learn to detect key generators and crack them.
Before you go to the next chapter, go over the steps again, and also go over the protection mechanism detection and modification.
This tutorial was written by Tech Lord <http://blacksun.box.sk>
-Spyda
How to crack software free and Run the trial version forever latest 2013
Today I am sharing how to crack software and run the trial version forever latest free 2013 crack. so what is crack? Have you ever the downloaded the software but
it was in trial? After sometime it had expired so then you are in
trouble but you still needed it so well if you want to forever activate
it without serial key and then you need the crack.
Before the starting with a crack you should know that the basic thing how these trial version software are run or programmed. This software always comes with the one month trial period and then after which they will be expire. When this software are installed for first time they make the entry of Installation Time, Date etc. And in the Windows Registry so whenever we run this software so they compare current system time and date with the new installation time and date. Thus they make out the whether trial period is the expired or not.
Download the software Download Runas Crack software
Tips to follow simple 4 steps:
STEP#01:
The Download this utility then has it ready all the time.
STEP#02:
As soon as you install the any trial version software’s and just note down the time and date of the installation.
STEP#03:
So inject the expiry time and date in RunAsDate v1.12 tool and it is the always safe you put in the date which is the prior to your expiry date and time.
And in the last step After the expiry always run such software’s and using RunAsDate v1.2 tool Thus trial version of software will run the forever.
Note:
This is the guide to instruct interested the parties how the crack could be performed on the new and latest software. Software piracy is the illegal in the most locales.
Before the starting with a crack you should know that the basic thing how these trial version software are run or programmed. This software always comes with the one month trial period and then after which they will be expire. When this software are installed for first time they make the entry of Installation Time, Date etc. And in the Windows Registry so whenever we run this software so they compare current system time and date with the new installation time and date. Thus they make out the whether trial period is the expired or not.
Why we Need it?
Manually changing a system time and date
to an earlier time and date will not be the right and final solution so
finally to overcome this there is the simple and very easy tool
“RunAsDate v1.12” .
Why we Used This Software?
RunAsDate v1.12 is the small utility that allows you to run the program in the time and date that you specify it. This utility does not change a current system time and date of the computer but it’s only injected the time/date that you will specify into a desired application.Download the software Download Runas Crack software
Tips to follow simple 4 steps:
STEP#01:
The Download this utility then has it ready all the time.
STEP#02:
As soon as you install the any trial version software’s and just note down the time and date of the installation.
STEP#03:
So inject the expiry time and date in RunAsDate v1.12 tool and it is the always safe you put in the date which is the prior to your expiry date and time.
STEP#04:
And in the last step After the expiry always run such software’s and using RunAsDate v1.2 tool Thus trial version of software will run the forever.
Note:
After expiry of software don’t run such software directly else crack will no longer the work.
Warning!!!!!
This is the guide to instruct interested the parties how the crack could be performed on the new and latest software. Software piracy is the illegal in the most locales.
How to get started in the art of cracking
Introduction:
————-
Tons of new programs are coming out each day… But the bad thing is that
most of them are shareware, which means that you have to pay to get the full
version (most of the time, when you’ll register, the creators of the program
will e-mail you an unlock code)… But there are some guys called “crackers”
who can modify the program so that you don’t need to pay to get the full
version. In this tutorial, you’ll learn how to crack programs (except VB
programs). I hope that you’ll enjoy it.
———————————————-
| |
|1) Programs that you’ll need to get started |
|2) Basic things about cracking |
1) Programs that you’ll need to get started
—————————————-
Here’s the list of programs that you’ll need to get to start cracking:
WinDisassembler
Hex Workshop
Hacker’s View
2) Basic things about cracking
—————————
Please remember that in this tutorial, I expect that you never cracked a
program, so it should be easy for beginners.
Here is, step by step, what you have to do to crack a program which needs a
name and a serial number (assuming that there’s no good protection):
a) Run the program
cool.gif Go to the place where you can enter your name and a serial number
c) Type your name and any serial number
d) Write down (or memorise) the error message
e) Copy the program’s exe to .bak (for backup) and to .w32
f) Disassemble [progname].w32 with WinDisassembler
g) Click on search -> search. Type the error message, and click on search
h) Scroll up until you find this “Referenced by a (U)nconditional or
©onditional Jump at Address: | blabla” (where blabla is the address)
i) Go to this address by scrolling up (the addresses are writen on the left)
j) There should be “jne” written at this address.
h) Double-click on the line and memorise the offset (written on the status bar)
i) Launch hacker’s view and edit the exe files
j) Press F4 and select Decode Mode
k) Press F5 and type the Offset.
l) Press F3 and type 74 (which will change jne to je)
m) If the program isn’t very securised, it should be cracked now!
n) Run the program
o) Type your name and any serial number
p) It should work!
Note: If it didn’t work, then it means that the program is more protected.
you have to learn more about assamble language and practice hard to crack advanced softwares.
Subscribe to:
Posts
(
Atom
)
