From 5903d13bb3162fa99bd1a0d73429414a68b5b6c3 Mon Sep 17 00:00:00 2001 From: _xeroxz Date: Tue, 20 Oct 2020 07:58:16 +0000 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e8097a9..a2fab09 100644 --- a/README.md +++ b/README.md @@ -25,8 +25,8 @@ nasa-mapper is like every other driver mapper except the driver is not mapped in ### How? memory that is going to be executed in ring-0 in usermode?? SMEP??, well just because the memory is mapped into usermode does not mean it is usermode accessable. nasa-mapper allocates -the driver in a runtimebroker.exe and then makes all the memory in runtimebroker.exe kernel memory & makes it executable. nasa-mapper then inserts a pml4e at index 70 into desired -processes. +the driver in a runtimebroker.exe and then makes all the memory in runtimebroker.exe kernel memory & makes it executable. nasa-mapper then inserts a pml4e at index 70 into a desired +processes thus mapping the usermode unaccessable memory into the process. ### Why?