How to obfuscate fat-jars?
- Thread starter LamerGamerYT
- Start date
- Status
PebbleHost
High performance, consistent uptime and fast support. Minecraft hosting that just works.
I have added you on discord.
I know we can use proguard, I have tried to do it, but failed to do so.
Any specific one you recommend?
Thanks, I'll take a look.
I would need your Discord Tag. I have many requests and no idea which one is you.
Regarding an obfuscator,
I specifically own Stringer, ZKM, and Allatori.
If you want a recommendation, I would say it depends on your needs.
If you wish to obfuscate resources as well, Stringer is your only choice.
If you want the best 'renaming' customizability, I would go for Allatori.
General obfuscation to prevent code theft would be ZKM.
Obviously, your best choice, given unlimited resources would be to mix the best features of each - Allatori for renaming, ZKM for code flow and string encryption, Stringer for resources (and maybe a bit of extra code flow for sensitive classes).
Last edited:
Allatori and ZKM are too expensive. I have Stringer as I had got it for a mc plugin project. Don't know if that can obfuscate fatjars..
What is a fatjar? Never heard of this term.
Stringer is the best obfuscator out there for protection, if you have it just use that.
Fatjar means a jar with external dependencies.
Oh, then yes Stringer would do the job perfectly. Stringer obfuscates code but it doesn’t rename fields, methods or class names.
I’ve never heard of ZKM9. I’m pretty sure Stringer can’t be deobfuscsted by an open source deobfuscator either, I’m yet to see one that does
Guys, let's stick to the point, can any of you help me obfuscate a fatjar?
Yes, Stringer would work as it doesn't rename methods/fields etc. You should also try what Notifyz said and see which works best for you. As long as methods, fields etc that are being used by external jars don't get renamed then it should work fine.
I don't even use obfuscators, the best one I've heard of is Stringer but then again I don't actually use obfuscators because I have no use for them, so I wouldn't know which the best one is.
When an obfuscator's bytecode transformations can be successfully cracked and a tool or reverser can create an algorithm which produces a legible, semantically equivalent section of bytecode, it is considered insecure or simply bad. Because of that, ZKM (and sometimes Dasho) is considered a significantly better choice than Stringer and Allatori (Same line of reasoning goes with encryption standards - you would get bashed for using DES in a sensitive production environment) because their techniques change routinely.
Directly from java-deobfuscator's Stringer transformers exist all the way up to Stringer 9 which appears to be the latest version according to the product site whereas java-deobfuscator's ZKM transformers exist all the way up to ZKM 8 and 9 (minus ZKM's method parameter change) which is completely outdated because ZKM is currently at version 11.
If I recall correctly, ZKM 9 can be deobfuscated by java-deobfuscator if the method parameter change isn't present. Java-deobfuscator cannot, however, deobfuscate anything above version ZKM 10 due to multiple protection scheme changes.
You use some random obfuscator (plz no Allatori), configure it, and obfuscate the project.
Directly from java-deobfuscator's Stringer transformers exist all the way up to Stringer 9 which appears to be the latest version according to the product site whereas java-deobfuscator's ZKM transformers exist all the way up to ZKM 8 and 9 (minus ZKM's method parameter change) which is completely outdated because ZKM is currently at version 11.
If I recall correctly, ZKM 9 can be deobfuscated by java-deobfuscator if the method parameter change isn't present. Java-deobfuscator cannot, however, deobfuscate anything above version ZKM 10 due to multiple protection scheme changes.
You use some random obfuscator (plz no Allatori), configure it, and obfuscate the project.
Last edited:
- Status
