Skip to content

Commit

Permalink
Update 2023-11-04-New_Fuzzer_Project.md
Browse files Browse the repository at this point in the history
  • Loading branch information
h0mbre authored Nov 4, 2023
1 parent 2027be5 commit 2625e06
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _posts/2023-11-04-New_Fuzzer_Project.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,4 +51,4 @@ Going a bit deeper, this setup requires us to sandbox Bochs and run it inside of
Secondly, it also means that the entirety of Bochs' state will be contained within our sandbox, which should enable us to reset Bochs' state more easily instead of it being a remote process. In a paradigm where Bochs executes as intended as a normal Linux process for example, resetting its state is not trivial and may leave you making either Kernel modifications or writing your own Kernel driver. Neither of which I feel like doing for the simple purpose of resetting Bochs.

So in general, this is how our fuzzing setup should look:
![](/assets/images/pwn/FuzzerArch.PNG
![](/assets/images/pwn/FuzzerArch.PNG)

0 comments on commit 2625e06

Please sign in to comment.