From a94df1d1e7d839c8fdfaa1223d0242d7a21172bf Mon Sep 17 00:00:00 2001 From: xerox Date: Sun, 19 Apr 2020 11:39:12 +0000 Subject: [PATCH] Update README.md --- README.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 8bd8f71..e9ab5a9 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Before I begin, those who helped me create this project shall be credited. # Physmeme Given map/unmap (read/write) of physical memory, one can now systematically map unsigned code into ones kernel. -Many drivers expose this primitive and now can all be exploited by simply coding a few functions. +Many drivers expose this primitive and now can all be exploited by simply coding a few functions. ### What versions of windows does this mapper support? @@ -48,7 +48,9 @@ This scanning takes under a second since each physical range is scanned with a s # How to use There are four functions that need to be altered to make this mapper work for you. I will cover each one by one. These functions are defined inside of a `physmeme.hpp` and need -to stay inside of this file. This allows people to make different `physmeme.hpp` files for each driver they want to abuse. Modular code. +to stay inside of this file. This allows people to make different `physmeme.hpp` files for each driver they want to abuse. Modular code. + +When writing your driver you will need a custom entry point just like every other driver mapper. ### `HANDLE load_drv()` Load driver must take zero parameters and return a handle to the driver. Here is an example of this: @@ -148,6 +150,3 @@ right now your entry point should look like this: ```cpp NTSTATUS DriverEntry(PVOID lpBaseAddress, DWORD32 dwSize) ``` - -You can change this as you see fit. Note you need a custom entry point like any other driver mapper requires. -