This commit is contained in:
parent
e794c037e8
commit
25c79da4f9
4 changed files with 15 additions and 10 deletions
|
@ -1,7 +1,6 @@
|
|||
#import "../lib.typ": etal, eg, ie, jfl-note, jm-note
|
||||
// #import "X_var.typ": *
|
||||
#import "../lib.typ": jfl-note, jm-note
|
||||
|
||||
#import "../lib.typ": todo, etal, APK
|
||||
#import "../lib.typ": todo, etal, APK, eg, ie, pb1, pb1-text
|
||||
|
||||
== Evaluating Static Analysis Tools <sec:bg-eval-tools>
|
||||
|
||||
|
@ -127,4 +126,6 @@ DroidBench@Arzt2014a
|
|||
Reaves #etal raised two major concern for the use of Android static analysis tools.
|
||||
First, they can be quite difficult to setup, and second, they appear to have difficulties analysing read-world applications.
|
||||
This is problematic for a reverser engineer, not only do they need to invest a significan amont of work to setup a tool properly, they do not have any guarantees that the tool will actually manage to analyse the application they are investigating.
|
||||
#todo[Ref to pb1 and rasta.]
|
||||
Hence our first problem statement #pb1:
|
||||
|
||||
#pb1-text
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue