Miscellaneous Primarily as a Open Source developer, this book is not the most obvious choice for review. Of course, as a developer of free software I am usually trying to promote the liberal copying and modification of my software. However, I enjoy reading most books in the realm of computing and technical know how so I thought that I would take the plunge and read it anyway. It takes the reader through a twisting maze of cracking methods, their counter measures and so forth. It provides well written, working examples to show exactly how each counter cracking method works, so that the reader might gain a better insight into the methods a cracker might use to circumnavigate any protection written in by the lowly software developer.
|Genre:||Health and Food|
|Published (Last):||6 March 2015|
|PDF File Size:||2.40 Mb|
|ePub File Size:||4.46 Mb|
|Price:||Free* [*Free Regsitration Required]|
No part of this work may be reproduced or transmitted in any form or by any means electronic or mechanical, including photocopying: recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher Crackproof Your Software is an English version of Cracking a jak se proti nemm brinit, by Pavol Cerven the original Czech version X , copyright C by Computer Press. English translation prepared by Skrivanek Translation Services Trademarked names are used throughout this book.
Rather than use a trademark symbol with every occurrence of a trademarked name, we are using the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark Publisher: William Pollock Editorial Director: Karol jurado Cover and Interior Design: Octopod Studios Composition: 1 Design, LLC Copyeditor: Andy Carroll Indexer: Broccoli Information Management Distributed to the book trade in the United States by Publishers group West, Fourth Street, Berkeley CA; phone;fax Distributed to the book trade in Canada by Jacqueline Gross Associates, Inc, One Atlantic Avenue, Suite , Toronto, Ontario M6K 3E7 Canada; phone: ; fax For information on translations or book distributors outside the United states and canada, please see our distributors list in the back of this book or contact No starch Press Inc.
While every precaution has been taken in the preparation of this work, neither the author nor No Starch Press, Inc shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directhy or indirectly by the information contained in it Library of Congress Cataloging-in-Publication Data Carven Pavol [Cracking a jak se proti nemm brinit.
Computer security. Data protection. Computer crimes. Title QA My father bought a Pc about four years ago, and if not for that PC, this book probably would not exist.
When I finished this book, I was 23 years old. I have tried several programming languages but have remained faithful to assembly because I think it is the clearest and the most beautiful programming language. What you write in assembly is exactly what you will find in the compiled version - nothing less and nothing more In the days of dos I dealt with the problems closest to assembly - viruses, and even dreamt about working for an antivirus software company.
When Windows 9x appeared, assembler was used less and less and there were also fewer viruses at least fewer assembly viruses. It will also be useful to programmers creating freeware who wish to protect their source code The idea to write a book like this came to me some time ago when realized how poorly the topic is covered and how difficult it is to acquire the information necessary to adequately protect software.
When was involved with game production in the Czech and Slovak Republics, I was astonished at how simple their protection was, and that very often they had no protection at all yet it is so easy to protect software at least at a basic level The problem lies in the lack of information and experience in this field.
What creators of a program or game would want to find their product, whether shareware or commercial software, pirated on the Internet the very day of the release? That would definitely result in reduced sales Good software protection prevents the cracker from removing the protection correctly.
Of course, a successful crack will appear in the course of time, but the time you buy is money earned. Really good protection will buy a considerable amount of time and will engender several versions of the crack, some of which will not work properly. The examples are all in assembler, but they are written as comprehensibly as possible and are accompanied by footnotes in a source code. I chose not to use visual Basic because most examples cannot be written in it. This is certainly not a perfect solution, but it is better than no protection at all Publishing cracker Tricks This book took considerable effort to write.
I had to do a good bit of research, and most of what I present here comes from the web pages of crackers. However, keeping it secret would be counterproductive. The fact is, crackers are very we formed, while developers have virtually no resources. This situation will hopefully change in the future, and I will be very glad if this book helps in this effort My thanks go to all the people without whom this book would never have been written First, my special thanks to my friend Linda and my family, who tolerated my late-night sessions and my bad mood in the mornings when I had to go to work Thanks to my Internet friends EliCZ Thanks for all the help and for your faultless source code.
There is hardly a better system programmer than you, really Ivan Bartek Thanks for everything; I look forward to our future cooperation Miroslav Bambosek You helped me a lot with your keen observations and your help with c examples. Crackers are the people who try to remove the protection from your software so that it can be illegally distributed.
Mostly, crackers are very smart people who will work on removing software protection for days at a time, and in extreme cases even for weeks, for the challenge of it. Crackers post their cracks and information for free, after all. They re not making money off your software, though the people who use their cracks are saving money. Crackers use two kinds of utilities for breaking software protection --debuggers and disassemblers Debuggers Debuggers allow crackers to trace an application, instruction by instruction, and to stop it at any point and follow its important sections.
But on the other hand, higher-level programming languages offer fewer possibilities for creating really good protection. Everything has its bright and dark sides Disassemblers Disassemblers can translate application code back into assembler.
One advantage that disassemblers offer over decompilers is that they always translate into assembler, so the cracker has to know only that one language. The quality of the resulting translated code depends on the quality of the disassembler. The best disassemblers even comment on the translated code which makes the code that much easier to understand.
For example, if the cracker finds a"Wrong serial number"string and locates its place in the code, he will be able to find the part of the code that protects the application. At that point, nothing can prevent him from studying the protection and breaking it Decompilers Decompilers can translate application code back to source code. There are for example, decompilers for Delphi, Visual Basic, and Java.
CRACKPROOF YOUR SOFTWARE PROTECT YOUR SOFTWARE AGAINST CRACKERS PDF
Bazshura She has you have to assume a good deassembler and decompiler, and is fluent in the assembly language of your code. I highly protext this book for software developers. If for any reason your order is not available to ship, you will not be charged. Great condition for a used book!
Crackproof your software : the best ways to protect your software against crackers