This commit is contained in:
parent
de9674f09c
commit
96b8d24b29
13 changed files with 26 additions and 24 deletions
|
@ -1,4 +1,4 @@
|
|||
#import "../lib.typ": todo, SDK, API, ART, DEX, APK, JAR, ADB, jfl-note, APKs
|
||||
#import "../lib.typ": todo, SDK, API, ART, DEX, APK, JAR, ADB, jfl-note, APKs, midskip
|
||||
|
||||
== Collecting Runtime Information <sec:th-dyn>
|
||||
|
||||
|
@ -77,7 +77,7 @@ Nonetheless, the benefit of our implementation is that it only requires an #ADB
|
|||
Of course, to analyse a specific application, a reverse engineer could use an actual smartphone and explore the application manually.
|
||||
It would be a lot more stable than our automated batch analysis setup.
|
||||
|
||||
#v(2em)
|
||||
#midskip
|
||||
|
||||
Now that we saw both the dynamic analysis setup and the transformation we want to perform on the #APKs, we put our proposed approach into practice.
|
||||
In the next section, we will run our dynamic analysis on #APKs and study the data collected, as well as the impact the instrumentation has on applications and different analysis tools.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue