Programming Without Cracking Danger - Watermarking Versus Program Protection
View PDF | Print View
by: jsogiros
Unlawful actions necessitate supplying proof for the source of the own work in court. It adds up to the job so that software piracy is a leading obstruction for creators. It is not so easy to demonstrate rightful ownership of pirated applications, but the author has more such affairs to attend to, as well. This affair systematically aggravates piracy concerns, only it is exactly what software watermarking answers. It embeds undisputable property data in a program. Nonetheless, the doubt persists whether the technique is effective.
A software provider requires customers to pay a licensing fee to register the software. Accordant to this example, the marketer will transmit a key after buying to the client permitting for validated utilisation of the software. Normally, executing the software without the proper license isforeclosed through verification code, integrated in the software.Well, at least, that is the usual processing. Nevertheless, a software reverser might hack the software and generate a key, or he might kill the checking code in the software such that the software can be operated without a key. It is difficult to secure versus reversing activities. Often, the creator can only prevent hacking attempts. That's why he should try to foresee all kinds of assaults on his software and make it as tricky to pirate as feasible. Of late investigated methods in watermarking can aid in this issue.
In the past decennium, Microsoft Intermediate Language and Java Bytecode have known a stable grow in employment. These formats look nearly like code and decompilation into the original source is almost simple. Accordingly, this allows for not so honest developers to steal a contender's secrets and even to employ a rival's code in the own application. In the comparable way, these formats are easily reversed. For the developer, this processing can accomplish a significant reduction in production time. For the reverser, it's frequently as easy as to convert one individual byte in the application to get around a registration strategy. Now, it is mostly super problematical to follow it back to the pirate if a cracked software is sold or simply distributed unpaid. And without special systems, it is pretty difficult to demonstrate in court an unethical competitor has taken advantage of a stolen business deal.
Aiming to prevent the infringement of copyright software watermarking and the more specific fingerprinting are systems that have been analysed in academic environment as well as in companies. The usable techniques are similar to those of media watermarking. In digital media watermarking, a unique identifier is included in data such as audio, text, video, or images. As a matter of fact, these systems raise limited mistakes in the media that are imperceptible by the human sensory systems. Program data is much more sensible to modifications. This makes a big divergence for applications and the watermark cannot be implanted just anyplace. Instead,implanting the unique identifier in programs should not break the original working in any fashion, exactly because unreliable treatment might produce the software to crash.
So, software watermarking implements the watermark - a unique identifier - into a program. If the identifier uniquely demonstrates the vendor of the program, then the identifier is a watermark in the form of a copyright notice, the watermark is called a fingerprint if the identifier uniquely identifies the legitimate buyer of the computer program. The usage of a secret key is an important aspect of watermarking. Through the function of the key, the watermark is incorporated into the application, making a - though barely - otherwise application. Still, the watermark can not point to the real pirate of the illegal activity. Thus,the problem remains: a watermark can evidence property but it . To bestow such characteristics to the watermark, it needs a fingerprint, in fact, the fingerprint information is a watermark holding information from the individual client.
It exists two general categories of watermarking algorithms, static and dynamic. A dynamic algorithm relies on information gained during execution of the application to apply or extract the watermark. The code and information of the software - like on disk only - is used in the static algorithms . There are few publishings describing the evaluation of these algorithms. A diversity of software watermarking techniques have been investigated though. Remark there are less dynamic watermarking algorithms than static since it is less complicated to obscure in binary source code on disk than at runtime.
As well the application of watermarks - in static as in dynamic data structures - is a feasible approach. Existent arrangements fetch usable programs resulting to software resiliency for a mixture of unlawful attempts while the watermarks can be distilled efficiently by the lawful owner. It must be mentioned coders still need to incorporate complementary security techniques to best guard versus cracking approaches. Each implemented sheltering system enforces general protection thus making attempts more tricky altogether.
About the Author
As a hobbyist writer, Sogiros is commenting about security because in his job as program security developer, he resolves issues comparable to "What is the optimal security software for the own 64 bit program?" all day.
Rating: Not yet rated
Login to vote