[Soot-list] Analyzing Android

[Steven Arzt]

Hi Bernhard,

The DexClassProvider works for dex files and not for JAR files. What one would need to also analyze dex files contained in jar files is to extend the SourceLocator class so that when it scans through a JAR file, it detects dex files inside there as well, extracts them, and passes them to the Dexpler component. That should not be too hard to accomplish in principle, but there are several details to take into account in case you also want to write the loaded classes back out after some transformation.

Soot needs the android.jar file whenever it reads dex files. This JAR file contains the Android system classes. You might be able to patch Soot so that it does not directly fail if no android JAR is specified and work with phantom classes for everything that is missing, but I won't give any guarantees on the outcome.

Best regards,
  Steven

-----Ursprüngliche Nachricht-----
Von: soot-list-bounces at CS.McGill.CA [mailto:soot-list-bounces at CS.McGill.CA] Im Auftrag von Bernhard Berger
Gesendet: Dienstag, 25. November 2014 22:01
An: soot-list at sable.mcgill.ca
Betreff: [Soot-list] Analyzing Android

Hi everybody,

I’m trying to analyze some Android files and came across some jar files that contain dex files. Currently, Soot does not read dex files included in jar files. As far as I see, this can be solved by patching the DexClassProvider to work for .jar files as well.
The second problem I am facing is the fact that soot always expects an android.jar. Is there a way to activate the DexClassProvider without being forced to add an android.jar?

Regards, Bernhard

_______________________________________________
Soot-list mailing list
Soot-list at CS.McGill.CA
https://mailman.CS.McGill.CA/mailman/listinfo/soot-list