In Process vs. Out of Process memory editing

[motodrizzle]

Hello all,

I am new here and have really enjoyed sifting through the massive amount of content this community has to offer. Unfortunately, I have found myself in a position where I need to ask a few questions, please forgive me if these questions have already been asked.

My understanding is as follows:

Out of Process (OOP) memory editing is where a your program reads and manipulates the memory of a host process directly.

In Process memory editing is where your program injects code into a host process, in order to edit the memory on the host process' thread. This can be achieved through a hook to a method, such as directx9's EndScene() using Assembly code caves.

I may or may not be correct in my understandings, if not please correct me. What are the benefits of In Process editing? Does In Process editing remove the chance of OOP causing a cross thread exception? I would think that a code cave would be more intrusive than directly editing memory from another process.

[yellowspark]

Benefits of inprocess editing are that you can hook stuff more easly and call functions by typedef ,but nobody said you cant do that out of process
You can pretty much do everything outside of process what you can do in process,all depends how hard you try

[DarkLinux]

OOP is really Object-oriented programming, best to call it external. Microsoft has lots of extended function (Ex) that should help you out.