Wizzard/radarflow2-kvm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Janek 2024-01-08 00:31:47 +01:00 committed by GitHub
parent f027f80b34
commit 30afd26468
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 7 deletions

13
README.md

@ -1,8 +1,9 @@
# radarflow
# radarflow2
A Web radar for CS2 using [memflow](https://github.com/memflow/memflow)
## How can I run this?
There is two ways to run this, first way is using a KVM/QEMU setup to target a running VM to read memory out of it. The second way is using pcileech hardware, like a PCIe Screamer.
There is two ways to run this, the first way is using a KVM/QEMU setup to target a running VM to read memory out of it.
The second way is using pcileech hardware, like a PCIe Screamer.
### The KVM/QEMU method
First, you need to set up a virtual machine on linux using qemu.
@ -27,9 +28,13 @@ The needed Plugins are `memflow-pcileech` and `memflow-win32`.
Furthermore, you need to install some libraries, depending on your attacking PC's OS.
```
On Windows you additionally need to supply the proprietary FTD3XX.dll. It can be downloaded from the FTDI Website in the Application Library (DLL) column.
On Windows you additionally need to supply the proprietary FTD3XX.dll.
It can be downloaded from the FTDI Website in the Application Library (DLL) column.
On Linux you need to check-out and compile the leechcore_ft601_driver_linux project from the LeechCore-Plugins repository. On Linux the leechcore_ft601_driver_linux.so file currently has to be placed in /usr/ or /usr/lib. Alternatively LD_LIBRARY_PATH can be set to the containing path. Check the dlopen documentation for all possible import paths.
On Linux you need to check-out and compile the leechcore_ft601_driver_linux projectfrom the LeechCore-Plugins repository.
On Linux the leechcore_ft601_driver_linux.so filecurrently has to be placed in /usr/ or /usr/lib.
Alternatively LD_LIBRARY_PATH can be set to the containing path.
Check the dlopen documentation for all possible import paths.
```
Clone the repo on your attacking pc: