Request: offer JNI "security layer" too

MichaelRocks / paranoid

String obfuscator for Android applications.

Apache License 2.0

670 stars 79 forks source link

Request: offer JNI "security layer" too #41

Closed AndroidDeveloperLB closed 3 years ago

AndroidDeveloperLB commented 3 years ago

Instead of getting the strings from Java code, you could make it inside JNI, which is a bit harder to de-obfuscate...

MichaelRocks commented 3 years ago

I'm personally is not a big fan of native libraries because they sometimes fail to install properly and cause crashes in production. Maybe I'll consider moving obfuscation stuff into the native part but it's not going to happen soon.

AndroidDeveloperLB commented 3 years ago

It's just as an optional thing. It can help with a bit more security. It's harder to de-obfuscate code in native than in Java/Kotlin, no?

MichaelRocks commented 3 years ago

Sure, I totally agree, but the implementation can be quite complicated and doubt I'll have enough time for that in the nearest future.

AndroidDeveloperLB commented 3 years ago

I might be wrong, but I think StringCare does it.