Wrap Reflective DLL Readme.md to 80 columns

external/source/exploits/cve-2013-3660/Readme.md

@@ -1,36 +1,67 @@
 About
 =====
 
-Reflective DLL injection is a library injection technique in which the concept of reflective programming is employed to perform the loading of a library from memory into a host process. As such the library is responsible for loading itself by implementing a minimal Portable Executable (PE) file loader. It can then govern, with minimal interaction with the host system and process, how it will load and interact with the host.
+Reflective DLL injection is a library injection technique in which the concept
+of reflective programming is employed to perform the loading of a library from
+memory into a host process. As such the library is responsible for loading
+itself by implementing a minimal Portable Executable (PE) file loader. It can
+then govern, with minimal interaction with the host system and process, how it
+will load and interact with the host.
 
-Injection works from Windows NT4 up to and including Windows 8, running on x86, x64 and ARM where applicable.
+Injection works from Windows NT4 up to and including Windows 8, running on x86,
+x64 and ARM where applicable.
 
 Overview
 ========
 
-The process of remotely injecting a library into a process is two fold. Firstly, the library you wish to inject must be written into the address space of the target process (Herein referred to as the host process). Secondly the library must be loaded into that host process in such a way that the library's run time expectations are met, such as resolving its imports or relocating it to a suitable location in memory.
+The process of remotely injecting a library into a process is two fold. Firstly,
+the library you wish to inject must be written into the address space of the
+target process (Herein referred to as the host process). Secondly the library
+must be loaded into that host process in such a way that the library's run time
+expectations are met, such as resolving its imports or relocating it to a
+suitable location in memory.
 
-Assuming we have code execution in the host process and the library we wish to inject has been written into an arbitrary location of memory in the host process, Reflective DLL Injection works as follows.
+Assuming we have code execution in the host process and the library we wish to
+inject has been written into an arbitrary location of memory in the host
+process, Reflective DLL Injection works as follows.
 
-* Execution is passed, either via CreateRemoteThread() or a tiny bootstrap shellcode, to the library's ReflectiveLoader function which is an exported function found in the library's export table.
+* Execution is passed, either via CreateRemoteThread() or a tiny bootstrap
-* As the library's image will currently exists in an arbitrary location in memory the ReflectiveLoader will first calculate its own image's current location in memory so as to be able to parse its own headers for use later on.
+shellcode, to the library's ReflectiveLoader function which is an exported
-* The ReflectiveLoader will then parse the host processes kernel32.dll export table in order to calculate the addresses of three functions required by the loader, namely LoadLibraryA, GetProcAddress and VirtualAlloc.
+function found in the library's export table.
-* The ReflectiveLoader will now allocate a continuous region of memory into which it will proceed to load its own image. The location is not important as the loader will correctly relocate the image later on.
+* As the library's image will currently exists in an arbitrary location in
-* The library's headers and sections are loaded into their new locations in memory.
+memory the ReflectiveLoader will first calculate its own image's current
-* The ReflectiveLoader will then process the newly loaded copy of its image's import table, loading any additional library's and resolving their respective imported function addresses.
+location in memory so as to be able to parse its own headers for use later on.
-* The ReflectiveLoader will then process the newly loaded copy of its image's relocation table.
+* The ReflectiveLoader will then parse the host processes kernel32.dll export
-* The ReflectiveLoader will then call its newly loaded image's entry point function, DllMain with DLL_PROCESS_ATTACH. The library has now been successfully loaded into memory.
+table in order to calculate the addresses of three functions required by the
-* Finally the ReflectiveLoader will return execution to the initial bootstrap shellcode which called it, or if it was called via CreateRemoteThread, the thread will terminate.
+loader, namely LoadLibraryA, GetProcAddress and VirtualAlloc.
+* The ReflectiveLoader will now allocate a continuous region of memory into
+which it will proceed to load its own image. The location is not important as
+the loader will correctly relocate the image later on.
+The library's headers and sections are loaded into their new locations in
+memory.
+* The ReflectiveLoader will then process the newly loaded copy of its image's
+import table, loading any additional library's and resolving their respective
+imported function addresses.
+* The ReflectiveLoader will then process the newly loaded copy of its image's
+relocation table.
+* The ReflectiveLoader will then call its newly loaded image's entry point
+function, DllMain with DLL_PROCESS_ATTACH. The library has now been successfully
+loaded into memory.
+* Finally the ReflectiveLoader will return execution to the initial bootstrap
+shellcode which called it, or if it was called via CreateRemoteThread, the
+thread will terminate.
 
 Build
 =====
 
-Open the 'rdi.sln' file in Visual Studio C++ and build the solution in Release mode to make inject.exe and reflective_dll.dll
+Open the 'rdi.sln' file in Visual Studio C++ and build the solution in Release
+mode to make inject.exe and reflective_dll.dll
 
 Usage
 =====
 
-To test use the inject.exe to inject reflective_dll.dll into a host process via a process id, e.g.:
+To test use the inject.exe to inject reflective_dll.dll into a host process via
+a process id, e.g.:
 
 > inject.exe 1234