Re: Cracking methods and how to stop them
Posted: Sat May 22, 2010 11:56 pm
So far no protection i know of lasted 1 year. There are allways some shortcuts that hackers find. For example on a VM protected code in lots of cases the hacker don't have to understand the VM and interpret the opcodes. It's a matter of patching the VM in the right place with a little proc that checks for conditions to only alter the behaviour of a specific command in a specific subroutine of a routine in bytecode.utopiomania wrote: Protection will be broken eventually, but if a hacker needs to work 24/7 for the next 12 month to
crack my little crackme, then I'm a winner, and the cracker is a looser.
That shortcuts mostly break your effort you put into developing anti-cracking stuff. And the more complex your protection is, the more possible shortcuts are there, that you miss.