Repository navigation
Iteration 2 Alpha
In this iteration we want to present the alpha.
- Finish last stages goals.
- Combined Frida in our project.
- Learn how to work with visual studio- dumpbin tool
- Use dumbin to read a dll file and write a function that will only take out the functions name that are written in it.
- Write a script Frida that identify when a function has been read.
- Creaing a function that send to our firda project process, dll file, function.
- Writing a testing plan
links to issues and boards
8 week
- Frida
- Visual studion- Unit test
This iteration was our longest iteration so far. In this iteration we finished what we had left from the previous iteration and started the new tasks. We learned about a tool named dumpbin that allows you to read dll files. We have developed a function that uses dumpbin to extract only the names of the functions in it. Up to this point, we had a database for each running program that contained all the dll files that the program was used. Now we have created a method that creating a database for dll that contatins all the functions name that exist in it. Now we have created a new dll project that will contain Firda and write the functionality we want. Because this project is a dll we can access its functions from our original project. We had to write a new project because frida is written in c and we do our project in c#. After we created the new project, we wrote a script that, with the help of frida, we will inject it into the process that we chose, and we will be able to track function calls. We then had to recycle the dll database and improved the script by opening the database and updating each call for a function. Next we called frida methods through our project and fixed bugs found. In addition we have developed a number of new functions, including a function that print us a summary for the process we are testing. In the last step we wrote a testing program for our project to see correct behavior of all functions and different endpoint identifications.