Quote:
Originally Posted by hellrider
Not to sound pessimistic, but everyone should realize that anyone with passable knowledge of ARM assembly can patch any of these checks. Piracy protection is a losing battle, so just try to make the cracker expend as much time and effort as possible. Though, once he patched the app, he can send it to the horde of 12 year olds eagerly awaiting their new app.
|
Oh there are multiple ways to work around that.
first, do your checks often, and most importantly, DO NOT reuse the picracy checks. resusing the code allows for an easy point of entry to circumvent the checks.
second, once you understand the algorithm for the anti piracy code, alter the algorithm enough to preserve the logic flow, but alter the generated ASM code. This will make it harder to find ALL the AP checks in your code.
third, I think the combination of detecting the stripped encryption and debugger launch detection should be enough to deter most crackers.
Can I stop 100% of the attacks? probably not, but I will make it as hard as possible.
