From 66b52ce777931a8690ae9c2bdf1d71c642b4fd52 Mon Sep 17 00:00:00 2001 From: _xeroxz Date: Sat, 24 Oct 2020 01:21:01 +0000 Subject: [PATCH] Update README.md --- README.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/README.md b/README.md index 53057a8..a97601a 100644 --- a/README.md +++ b/README.md @@ -40,8 +40,4 @@ processes pointing at the allocated driver in the runtimebroker, thus mapping th Keeping your driver out of the kernels paging tables. Most driver mappers map a driver into a kernel pool (ExAllocatePool). Physmeme, Kdmapper, Drvmapper, all do this, its easily detected and easy to dump. This keeps your driver inside of your context :) -I guess you can call this physmeme v2? You can use any driver that exposes physical memory read/write with this driver mapper, simply replace the vulnerable driver inside of raw_driver.hpp. - -# Spectre - -Please disable spectre/meltdown when using nasa-tables/nasa-patch/nasa-mapper. You can download a program to disable spectre/meltdown [here](https://www.grc.com/inspectre.htm). \ No newline at end of file +I guess you can call this physmeme v2? You can use any driver that exposes physical memory read/write with this driver mapper, simply replace the vulnerable driver inside of raw_driver.hpp. \ No newline at end of file