these-android-re/thesis
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages 1 Wiki Activity Actions

fix typos up to ch 3
All checks were successful
/ test_checkout (push) Successful in 50s
Details

Browse source
This commit is contained in:
Jean-Marie 'Histausse' Mineau 2025-12-21 13:37:29 +01:00
parent d34e403ca5
commit 3b5df50248
Signed by: histausse
GPG key ID: B66AEEDA9B645AD2
16 changed files with 1629 additions and 248 deletions
Download patch file Download diff file Expand all files Collapse all files

3
2_background/1_intro.typ
View file

@ -3,9 +3,10 @@
== Introduction
In order to understand the challenges of reverse engineering Android applications, we first need to understand some key concepts and specificities of Android.
In particular, the format in which applications are distributed, as well as the runtime environment that runs those applications, is very specific to Android.
In particular, the format in which applications are distributed, as well as the runtime environment that runs those applications, are very specific to Android.
To handle those specificities, a reverse engineer must have appropriate tools.
Some of those tools are used recurrently, either by the reverse engineer themself, or as a basis for other more complex tools that implement more advanced analysis techniques.
// NOTE: "reverse engineer themself": both themself and themselves are correct, I prefere themself here because it's one specific non gendered engineer.
Among those techniques, the ones that do not require running the application are called static analysis.
Over time, many of those tools have been released.