![]() |
|
#3
|
|||
|
|||
|
In a weird sort of way, you can think of us a "program psychologists". The software WANTS to run, it's only happy when it does what it was designed to do. It usually has inperfections that restrict it from doing this, we remove those inhebitions... Happy software is running software.
OK, enough... There's the obvious challenge, "because it's there". Cracking's fun and relaxing, with the occasional pulling out of ones own hair. It's gratifing to see a program run the way it should, without all the nasty protection. But I'm not in it for the "cracking", but rather the reversing. Sometimes the most challenging code to reverse is the protection. If you think about it, these routines are usually written to be hard to understand. By becoming apt at dealing with code that is intentionally convoluted, regular routines become childs play. It's a bit of "practice makes perfect". My motivation is knowledge and experiance. I become a better reverser by cracking, and I become a better programmer by reversing. I nearly always pay for the software I use, I don't release "cracks". My trophies are the algorythims, and I never use them until I understand them well enough to come up with my own. I doubt you'll find any "thiefs" on this or Woodmans forum. No one here is out to hurt software developers, most of us ARE software developers. Cracking improves your debugging skills. Reversing improves your coding skills. These skills would be nearly imposible to pick up any other way. So, dump the VB, get a C++ compiler and Olly, and come over to the Dark Side. You won't regret it...
|
|
|