erf, not good, but it's something at least
All checks were successful
/ test_checkout (push) Successful in 1m47s

This commit is contained in:
Jean-Marie 'Histausse' Mineau 2025-09-25 16:49:27 +02:00
parent c34eb1b838
commit fede0bd9b2
Signed by: histausse
GPG key ID: B66AEEDA9B645AD2
5 changed files with 42 additions and 36 deletions

View file

@ -2,7 +2,7 @@
== Conclusion <sec:bg-conclusion>
In this chapter, looked at the specificities of Android and the usual tools used as a basis for reverse engeenering applications.
This chapter, presented the specificities of Android and the usual tools used as a basis for reverse engeenering applications.
Many contributions have been done to static analysis, and benchmarks have been proposed to compare the different tools that resulted from those contributions.
Those benchmarks raised questions about the reusability of those tools and their capacity to handle real-world applications.
We then looked at a platform classes and class loading, a commonly recognised limitation of static analysis.
@ -13,10 +13,10 @@ The result of those analysis are often in an ad hoc format, making it difficult
A few exception as well as some static analysis tools proposed an interesting solution to this issue:
instrumenting the analyse application to encode the results of the analysis in the form of a valide #APK, a format any Android analysis tools should be able read.
We liked this solution and believe it should be studied further.
This process led us to our problem statements:
This process led us to explore three problem statements:
/ #pb1: #pb1-text
/ #pb2: #pb2-text
/ #pb3: #pb3-text
In the next chapters, we will endeavor to contribute to the Android reverse reverse engineering field by anwsering those problematics.
In the next chapters, we will endeavor to contribute to the Android reverse reverse engineering field by anwsering them.