Crackproof Your Software: Protect Your Software Against Crackers

Crackproof Your Software: Protect Your Software Against Crackers

by Pavol Cerven

Paperback(BK&CD-ROM)

$29.14 $34.95 Save 17% Current price is $29.14, Original price is $34.95. You Save 17%.

Product Details

ISBN-13: 9781886411791
Publisher: No Starch Press
Publication date: 11/15/2002
Edition description: BK&CD-ROM
Pages: 272
Product dimensions: 7.36(w) x 9.34(h) x 0.82(d)

About the Author

Cerven is a software developer with Alcatel. After a brief stint in the world of PC viruses, he now works to protect software against unauthorized copying.

Table of Contents

Introduction1
Chapter 1Basics5
Chapter 2Cracking Tools9
Chapter 3The Basic Types of Software Protection15
Chapter 4CD Protection Tricks41
Chapter 5Program Compression and Encoding: Freeware and Shareware53
Chapter 6Commercial Software Protection Programs75
Chapter 7Anti-Debugging, Anti-Disassembling, and Other Tricks for Protecting Against SoftICE95
Chapter 8Protecting Against Breakpoints, Tracers, and User Debuggers167
Chapter 9Other Protection Tricks185
Chapter 10Important Structures in Windows207
Chapter 11Suggestions for Better Software Protection225
Glossary231
About the CD232
Index233

Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews

Crackproof Your Software: Protect Your Software Against Crackers 3 out of 5 based on 0 ratings. 2 reviews.
Guest More than 1 year ago
Much of current software defenses against crackers consists of preventing or detecting breakins to your computer from across a network. The cracker is inherently at a disadvantage. For one, you (the sysadmin) have physical access to your machine. You can reboot it at will; compare signatures of installed programs against known signatures that are stored readonly; and you can install network analysers and other computers to check your main machine. But there is an entirely different cracker activity where she now has built in edges. This consists of where you write code that others can install on their computers. Your code can end up on a cracker's machine. She has (you have to assume) a good deassembler and decompiler, and is fluent in the assembly language of your code. You don't have it easy. Cerven explains the many measures you might take to protect the running of your code. Alas, for most of these, if not all, over time, a sufficiently talented cracker can find a countermeasure. The book is a tribute to human ingenuity. As a purely intellectual puzzle, you may find his explanations intriguing. He describes a small cottage industry of companies that offer licensing programs that try to control access to your code. The best known may be installshield. This is very common on Microsoft platforms. Also mentioned is flexlm, which unix sysadmins should find familiar. The bottom line is given in the last chapter. A list of suggested best practices. None of which are guaranteed to offer absolute protection. But the cumulative applications of these practices should act as a good deterrent. The only thing that seems to be missing is a discussion of code that comes on DVDs. He describes CDs. Surely by now some large code packages must come on DVDs. (Especially the games.)
Guest More than 1 year ago
As a renowned computer security expert once said, 'trying to make bits not copyable is like trying to make water not wet'. This book goes into detail on tricks to thwart attempts at running debugging tools against programs you develop. Many of the suggestions presented by the book are detailed with plenty of example code given, but are narrow in scope. As such, new debugging and disasssembly tools (which are not susceptible to these tricks) have probably been developed by the time you crack the spine. I have never heard of a commercial program which uses software based anti-crack mechanisms which has not been cracked. At one point in the book, the author suggests that, if possible, you make your program run in ring 0 to thwart some crack attempts. This suggestion alone makes me question the author's competence. This book is interesting if you are curious, but the techniques are a waste of time and completely ineffective. Preventing people from manipulating a program running on a computer they have full control over is impossible.