Update 2023-11-04-New_Fuzzer_Project.md

_posts/2023-11-04-New_Fuzzer_Project.md

@@ -32,6 +32,7 @@ This fuzzing architecture seemed to meet several criteria that I personally valu
 - it is pretty unique in its design compared to open source fuzzing tools that exist,
 - it can be designed from scratch to work well with existing flexible tooling such as LibAFL,
 - there is no source code available anywhere publicly, so I'm free to implement it from scratch the way I see fit,
+- it can be made to be portable, ie, there is nothing stopping us for running this fuzzer on Windows instead of just Linux,
 - it will allow me to do a lot of learning and low-level computing research and learning.
 
 So all things considered, this seemed like the ideal project to implement on the blog and so I reached out to Gamozo to make sure he'd be ok with it as I didn't want to be seen as clout chasing off of his ideas and he was very charitable and encouraged me to do it. So huge thanks to Gamozo for sharing so much content and we're off to developing the fuzzer. 
@@ -53,4 +54,6 @@ Secondly, it also means that the entirety of Bochs' state will be contained with
 So in general, this is how our fuzzing setup should look:
 ![Fuzzer Architecture](/assets/images/pwn/FuzzingArch.PNG)
 
-In order to provide a sandboxed environment, we must load an executable Bochs image into our own fuzzer process.  
+In order to provide a sandboxed environment, we must load an executable Bochs image into our own fuzzer process. So for this, I've chosen to build Bochs as an ELF and then load the ELF into my fuzzer process in memory. Let's dive into how that has been accomplished thus far. 
+
+## Loading an ELF In Memory