Closed BullyWiiPlaza closed 1 year ago
Basically, the problem here is because of the obfuscation in static constructors. It uses the stack trace to generate the key for the string decryption, but I still lack proper stack trace creation for the static constructors. I'm working on it, but for you, the best solution will be to disable the usage of stack trace in it.
Finally fixed, now this should work properly (already tested on your binary)
I wrote a simple Java program as follows:
Output:
I compiled the fat JAR (including the
Apache Commons Validator
libraries but minified usingmaven
). The JAR ran successfully. Then, I applied a Java-based obfuscator on top of it. The JAR still ran successfully. Now I usednative-obfuscator
to build thex64-windows.dll
and put it back into thenative-obfuscator
generated JAR. So far so good. Upon running, the JAR however breaks with an exception:Without the Java-based obfuscation step,
native-obfuscator
however works correctly in this case. Maybe you can figure out what goes wrong here: JARs.zip My transpiler command was standard with no special flags applied.Thank you very much.
P.S. Yes, I'm aware that this project is not production ready which is a pity but maybe more bugs can be fixed regarding 3rd party library or obfuscator compatibility. Even GraalVM does not seem to be the native compilation savior here either.