As a beginning programmer, the risk for a reverse engineer / cracker to be interested in your programs right now is very small.
As a start you should consider that protection from crackers really doesn't exist. What does exist, is protection from the casual user who would use your program in a way not allowed. As the mass interest in a program rises, even the casual user will find a solution provided by a more skilled reverse engineer.
Anyway, there are still programmers trying to avoid programs being reverse engineeres.
Some methods are
- dynamic code (self-modifying or generated on the fly)
- encrypted code which is temporarily decrypted
- code on external devices (dongles and so on)
- anti-debugging and anti-anti-debugging and anti-anti-anti-debugging ... code
Main Topics
Browse All Topics





by: Alan3285Posted on 2009-04-11 at 14:38:33ID: 24123608
Given that every processor out there (of whatever type you are programming for) is effectively a disassembler for your compiled code, you are onto a loser there.
I suppose you could write it really badly - that will make it harder for anyone to follow from source or from dis-assembled code!
Seriously though - why are you concerned about this at the beginning of your programming life? I would suggest you concentrate on writing excellent code that compiles quickly and efficiently and avoids bugs and security holes that most programmers leave in (buffer overflows being the most heinous crime and one of the most easily avoided out there!)
HTH,
Alan.