|
You have to have good skills in assembler or c++ to make an "uncrackable" protection. In fact, I doubt that there will be an uncrackable protection, but things may become harder.
Mmmh, first off all it should be totally confusing, not only for reversing newbies, but for also for the "hex-masters". Jumps and calls to useless places all throught the whole code just to do nothing, trying to hide the "good-boy area" as good as possible. Some non-reversible (standing brute-forcing) piece of code is the next thing to include (hard one?).
This is just for the beginning. Btw, have you already tried some reversemes or crackmes dealing with copy-protections? Maybe you'll find something to include in your one.
__________________
[b][i]Monty says:[/i][/b]
Here's a phone. Call somebody who cares.
Ah, Monday morning.... Time to pay for your two days of debauchery, you hungover drones.
I could crush him like an ant. But it would be too easy. No, revenge is a dish best served cold. I'll bide my time until.... Oh, what the hell. I'll just crush him like an ant.
|