Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question on DeobfuscatorHelper #57

Open
iadcialim opened this issue Nov 1, 2021 · 1 comment
Open

Question on DeobfuscatorHelper #57

iadcialim opened this issue Nov 1, 2021 · 1 comment

Comments

@iadcialim
Copy link

Hi @MichaelRocks great tool here!
I was just reading an interesting issue here #12
I am thinking of a way of hiding this too but as you said it cannot be done and using Proguard is the best way now to hide this class.

I did a simple reverse engineering on my Proguarded sample app and I can find the DeobfuscatorHelper here
Screenshot 2021-11-01 at 9 39 37 PM

Although public static String getString(final long id, final String[] chunks) is kinda messed up here but am I right to say that I can still use the public src code here: https://github.com/MichaelRocks/paranoid/blob/33a94e259f8008b024c6ca7be4ae61fc8380ea81/core/src/main/java/io/michaelrocks/paranoid/DeobfuscatorHelper.java and with the arrayOfString above, I can de-obfuscate and get the original string?

@MichaelRocks
Copy link
Owner

Hi @iadcialim,
Yes, you can get the original strings but you need to know to find their usages in code to do that. Unfortunately it's impossible to prevent deobfuscation of strings because the application itself should be able to deobfuscate the strings somehow. It means that you can use the same code as the app does and deobfuscate the strings but it becomes a little more difficult than without obfuscation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants