You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
scanner mod.rs
After getting the correct process -> determine process size -> split into chunks [4096 bytes?]
These chunks will be fed to the scan method (e.g. brute force or algo1)
We should get all this info together before / during init ScanResult struct
pattern
mask
begin_addr
size
handle to proc
var: bytesRead
var: oldVProtect
var: buffer to read data to
mbi
[1] VirtualQueryEx (get our MBI)
[2] loop over each chunk (mbi.regionSize)
[3] check that its good memory using virtualqueryex & mbi.State, mbi.Protect
[4] delete our buffer from last read
[5] if VirtualProtect ex (save original protext to var: oldVProtect
[6] Read Procress Memory
[7] Restore protect using VirtualProtectEx
[8] pass data to scan method
[9] did the scan method find it? break or continue
The text was updated successfully, but these errors were encountered:
to consider, we could just give the memory address range (base + size) of the process instead of giving 1 data chunk at a time. This way each scan method could optimize as needed/multi thread/etc.
scanner mod.rs
After getting the correct process -> determine process size -> split into chunks [4096 bytes?]
These chunks will be fed to the scan method (e.g. brute force or algo1)
We should get all this info together before / during init ScanResult struct
pattern
mask
begin_addr
size
handle to proc
var: bytesRead
var: oldVProtect
var: buffer to read data to
mbi
[1] VirtualQueryEx (get our MBI)
[2] loop over each chunk (mbi.regionSize)
[3] check that its good memory using virtualqueryex & mbi.State, mbi.Protect
[4] delete our buffer from last read
[5] if VirtualProtect ex (save original protext to var: oldVProtect
[6] Read Procress Memory
[7] Restore protect using VirtualProtectEx
[8] pass data to scan method
[9] did the scan method find it? break or continue
The text was updated successfully, but these errors were encountered: