One type of copy protection common in trail or beta software, allows a program to run only until a certain date. The copy protection mechanism often involves a process in which the software checks whether it should run and, if should, which functionality should be exposed. The following sample shoes a way, how to bypass or remove the copy protection sachem in order to use the product without extending the trail duration or in fact, without purchasing the full version. The vendor stipulates a time restrictions condition over the beta software in order to be license misuse and permitting the product to run only in a reduced-functionality mode until the user registers. Typically in copy protection, the user is obligatory to register first for the product before use.

A familiar type of restriction built into software is copy protection which is normally forced by software vendor in order to test the robustness of software copy protection sachem. When the source code is not provided, it is still possible to patch the corresponding software binaries in order to remove various security restrictions imposed by vendor as well as fix the inherent bugs in the source code. It is expected that their machine must be configured with the following tools The security researcher must have rigorous knowledge of Assembly Programming language. We just have only the executable version of a particular application which is in fact, a tedious task in context of Reverse Engineering. In simple term, what we are implying that we don’t have the actual source code indeed.

This time, we are confronting with an application which origin is unknown altogether. We have already done much of reversing of. Although, there are much of tools that can achieve the same objective but the beauty behind OllyDbg is that, it is simple to operate and freely available. The objective of writing this paper is to manifest, how to crack an executable without peeping its source code by exercising OllyDbg tool.

Ollydbg cracking