My customer want's me to protect the APK as good as possible. Currently I use the release (obfuscated) to protect it. But I found also a tool "DexProtector" which do similar things. But this cost a awful lot of money. Do you really think this is much better?
Are there any other alternatives that you know of?
My customer want's me to protect the APK as good as possible. Currently I use the release (obfuscated) to protect it. But I found also a tool "DexProtector" which do similar things. But this cost a awful lot of money. Do you really think this is much better?
Are there any other alternatives that you know of?
char* myString1()
{
return "I am obfuscated.";
}
char* myString2()
{
return "I am obfuscated too!";
}
... you catch my drift!
Despite not being 100% hacker proof (nothing is!), it's a lot harder to disassemble an .so library than a regular Java one.
If you're really interested in protecting your apk, by all means, get the ProBundle and read Fred's tutorial.
Obfuscating a string is useless IF you don't prevent the hacker from altering and running your code. He will just have to log the string content once deobfuscated (e.g. after you load it from the .so library).
The main purpose of obfuscation is to make the understanding of your code a lot harder, not to protect your data.