,----------------------------------------, |****************************************| |*,------------------------------------,*| |*| The "all new"-newbie tutorial! |*| |*`------------------------------------'*| |****************************************| `----------------------------------------' I. Preface Welcome, dear reader and newbie cracker! This tutorial (introduction is a better description) shall help and guide you through the world of cracking. Actually, this tutorial (aka tut) should be the first one you read because it will give you practical hints and advices and show you the first few steps. It will also give you answers to your "first" questions and probably a basic understanding of what cracking really is. II. The art of cracking By definition, cracking is the process of making a program with limitations fully functional or optimizing its appearance to the user. This includes: finding valid serial number(s), patching code, removing nag screens, etc. Such limited programs can exist as sharewares but demo programs and games are possible targets to a cracker. Crackers use a technique called reverse engineering, meaning, that the cracker has to analyze his/her targets more or less thoroughly (mainly in parts), understand the basic functionality of certain program routines and possess the knowledge on how to "break" (thus, crack) its protection/coding. Reverse engineering can also be helpful for other tasks like faking server response, avoiding CD checks, or even improving or bugfixing programs, etc.! Besides this, you can enhance your programming/debugging skills and improve your "logical thinking" capabilities (think of a kind of high tech crossword puzzle). Later on, when you realize "how things run" you will see, that the knowledge in cracking programs may become an advantage in cracking other things. This time I mean cracking in a non-literally way. Some people call this "reality cracking". I don't call it that way because it might give you a wrong idea of what this "reality cracking" means. Cracking is more than just using a disassembler, a debugger and a patcher. It is a way of thinking, realizing and solving problems of all types (not only software). In a nutshell, using another (or more) point(s) of view when looking at problems of various kind. I hope those words didn't scare you too much, I doubt they did. And if you haven't understood them right now, it doesn't matter. When the time is right (and you are more experienced) you will understand them (if you can remember this tutorial at that time at all). III. Issues on cracking I hope by now you know that cracking or reverse engineering programs MIGHT BE illegal in the country or part of the world where you are. Take this as a serious warning! You should always face the fact that your (future) cracking activities will work against the domestic copyright and/or software laws. If you should get caught for this, this is really only your own fault - you've been warned! So, if you are scared now or want to stay "clean" quit now and look for another hobby. If you think you are a tough guy/girl or you already knew that and don't care, read on. Cracking is a VERY time consuming activity. When you start learning it, you will have to read many tutorials and manuals and probably make your own notes of the more important stuff. Later on, when you are a bit more experienced with your cracking tools and techniques you will spend alot of time with the actual process of "finding a crack". And then again, if you succeed in cracking (your first) programs you will get kind of addicted to it (you will see!), ripping off more and more of your spare time. Also, a lot of patience is required! So take care. Again: you've been warned! Cracking can be VERY frustrating. Yes, especially when you start learning it and you try to crack your first program and you try and try, spending alot of time, and yet the damn program "isn't crackable" (of course it is and you know that very well :). At this point the newbies will be distinguished from the losers (actually there are no losers, read above paragraphs). But if you can make it and crack your first program you surely want to continue. Another aspect of "time consumption" and "cracking frustration": one day you might look back at what you have done as an active cracker and you may realize that the whole thing was a big f**king waste of (life) time. But this only depends on you. You may say 'it was a waste of time', others might say 'I've learnt alot in that time, it's ok'. Anyway, one thing is for sure: you can't mention cracking in your curriculum vitae (CV), neither should you shout out your abilities in public. It has to be your little secret, until the day cracking is legalized or all software is freeware :). But if you want to share or widen your skills, take care of who you can trust and who you can't. IV. Where and how to start It's always the same troubles for newbies in the beginning. Where and how do I start with learning? Where can I get (more) infos/tuts/ tools/manuals/targets? The answer is pretty easy: "Swim in the sea of information!". The Internet. No joke, I'm serious :). If you should be too lame to use search engines (you shouldn't be) or if you are tired of clicking through dozens of fake (porn) links trying to find a real cracking related site, you can come to IRC channels like #cracking4newbies or #learn2crack (both on EFNet) and ask for an URL. From this URL you can link to other cracking/tutorial pages and so on. Get as much information as you can get (and are worth getting it for yourself). Read and learn as much as you can! There are hundreds of tutorials and tips&tricks essays/writings/ docs and "crackme's" (little programs that are just there to be cracked). If you have read, understood and practised them all, you are either blind or a cracking guru, or both :). The important point is that you don't "use" tutorials based on one program on other programs, but that you understand WHAT was done, WHY this was done and HOW it was done! Understand the principle method and not the specific solution to a specific program. Get a feeling on what is important. If you have (detailed) questions about certain things you can either join (the/a) Newbie Forum or visit above mentioned IRC channels. That leads me to some notes on how to behave in cracking related IRC channels. Besides the standard "netiquette" and "IRC rules" take the following in mind: If no-one answers your question(s) either no-one knows or all are idling/away. If latter is the case, come back at a later time. Don't annoy channel users (and especially ops!) with floodings, cracking requests (go to #cracks or similar channels) or non-cracking related chats (mostly tolerated). Ahh, and yes, be nice. Some ops don't carry their @ (temporarily) when in channel. V. Abilities you should have before starting Not much to say here. Basically, the more you know the better it is (and the easier your start will be). Basic ASM knowledge is a MUST. (Don't worry, you don't have to be an ASM master at all). Additional knowledge of a high level programming language (like C, Delphi, Visual Basic) does help (and sometimes is necessary to crack a program). Also, you shouldn't be clueless about the MS Windows API (Application Programming Interface) and how it works. But time and experience will teach you alot and therefore it's not necessary to know everything in the beginning. You will soon find out what is necessary to progress. Of course you should know how to handle your cracking tools (ie. your disassembler, debugger, etc.). Manuals are (almost) always available. Read, read, read! (There are also some tuts just about the tools!). VI. Cracking ethics There are some points I'd like to mention too. I don't know if there's really a kind of cracking ethics but if not so, I want to put it up now (and maybe start a "public" discussion about it). Crackers crack software, not networks. Unfortunately, in hacker slang, a cracker is someone who breaks into a network and messes up with data or does other nasty things. So, please, if you start up with the hacking business, call yourself a hacker. Crackers do not earn money with cracking. I don't know if there ever was a cracker that cracked software for (a bigger amount of) money, but cracking should be and should stay a non-profitable "job". It's alright if you get some warez or other stuff for your efforts but keep it that short so that no-one can claim that you do this for a living. Also, you are encouraged to make your cracks "for educational/testing purposes only". That means people should buy the software if they (plan to) use it for a longer term. You just give them the ability to try out the unlimited version. However, what people do with your crack(s) is up to them. Crackers should be willing to share their knowledge. I don't mean to help those "I want to learn cracking in an hour" people but to help people that have a certain question. If you want to dedicate more of your time into teaching others your knowledge, write a tutorial and/or join one of the IRC cracking channels (read above). Or even start your own cracking/tutorial website. Crackers are responsible for themselves and their doings. Don't blame anyone or anything else if something goes wrong (ie. your computer crashed, the feds busted you, your friend(s) left you, etc.). Crackers are free to join a cracking/warez group to combine their abilities. You have to follow the group's rules/requirements then. Crackers are also free to stay as "freelancers" and just learn/work for them alone. Crackers shouldn't call carding a part of cracking (every lamer can do that). That's all I can think of now. If you think what I wrote is bullsh*t or want to add/modify something, let me know. Email address is given at the end of this writing. VII. Helpful links Here are some good starting points (to snoop around the net) for more information: http://beam.to/blackb (very good newbie site) http://www.InsideTheWeb.com/messageboard/mbs.cgi?acct=mb628842&TL=933112283 (the newbie forum) http://reverserlinks.cjb.net/ (list of many related sites) VIII. Closing words I hope this guideline/"tutorial #1" did help you to decide whether or not you should become a cracker. If you want to give comments, suggestions or criticisms to this writing, simply email me (see below). I also want to thank Eternal Bliss and WarezPup for "beta-reading" this thing and doing (minor) corrections. Now, have fun with (learning) cracking, keep the scene alive, cheers, RevX - RevX@gmx.at - Copyright (C) 2000 RevX, all rights reserved :). -