Sorry second post wasn't worded properly.
Yes, I was asking obfuscating one jar, rather than the entire
application. If that's a good approach and if that's safe to do.
That's why the second post, if using a jar on an application if it
could be easily extracted. Cause if you could there is no
The way to do it would be to put a few critical classes for the jar's
functions somewhere else, so that just having the jar wouldn't be
sufficient. Of course, you'd want to (perhaps manually) obfuscate
those few classes somehow.
There's no obfuscation scheme that's 100% secure, and even 50%
Can used jar files be easily extracted from an application by others?
I guess that would be my only concern doing this...
On Oct 5, 11:26 am, Moto medicalsou...@gmail.com wrote:
I'm a bit scared about obfuscating my application completely. I'm
afraid to run into issues where I can't figure out
Why would you think a JAR provides any obfuscation at all? I open them
as ZIP files all the time. Not to mention that Android doesn't even
run Java bytecode. Any JAR you put in your project's classpath is just
a source for Java bytecode that gets converted to Dalvik bytecode and
put into a file in
I think he means just obfuscate one jar, rather than the entire
application.
On Oct 5, 7:20 pm, Lance Nanek lna...@gmail.com wrote:
Why would you think a JAR provides any obfuscation at all? I open them
as ZIP files all the time. Not to mention that Android doesn't even
run Java bytecode. Any
Though I'll admit that his second post makes no sense in that context.
On Oct 5, 7:20 pm, Lance Nanek lna...@gmail.com wrote:
Why would you think a JAR provides any obfuscation at all? I open them
as ZIP files all the time. Not to mention that Android doesn't even
run Java bytecode. Any JAR
6 matches
Mail list logo
