- Jun 6, 2020
- 11,559
- 4,422
If we create a build with the obfuscator(Ver 1), then make a tiny change to the code like refactor a variable name. Will the next obfuscated build (Ver 2) be materially the same?
The practical reason for asking is this. Lets say someone cracks the obfuscation on Version 1 of an app. If the version 2 app code base is basically the same, would the obfuscation be mostly the same, making it very easy to re-crack version 2?
If so, would is it possible to randomize the obfuscation when an build is created? At least make them "re-crack" it every time a new version comes out.
In theory, a new version of an app, with a new obfuscation pattern, could be released monthly, weekly, daily ?? if someone were so inclined. Obviously, it wouldn't "prevent" cracking the code, but it could slow them down a bit.
I don't know much about this obfuscation "dark art"
so this may already be the way it works. In that case, I might learn something LOL.
Thanks much!
The practical reason for asking is this. Lets say someone cracks the obfuscation on Version 1 of an app. If the version 2 app code base is basically the same, would the obfuscation be mostly the same, making it very easy to re-crack version 2?
If so, would is it possible to randomize the obfuscation when an build is created? At least make them "re-crack" it every time a new version comes out.
In theory, a new version of an app, with a new obfuscation pattern, could be released monthly, weekly, daily ?? if someone were so inclined. Obviously, it wouldn't "prevent" cracking the code, but it could slow them down a bit.
I don't know much about this obfuscation "dark art"
so this may already be the way it works. In that case, I might learn something LOL.Thanks much!
برای دیدن لینک ها باید ثبت نام کنید