(Question);
(Question);
what is Virtual protect and what is it used for ??
REGARDS.
REGARDS.
What i know it is for:
1- It is For Convert Asm to C++ without WINAPI.
2- Its Used for most time,to protect a Pointer or Multiple Pointers with Bytes.
Example:
Nopping Way.
1- It is For Convert Asm to C++ without WINAPI.
2- Its Used for most time,to protect a Pointer or Multiple Pointers with Bytes.
Example:
Nopping Way.
Originally Posted by darlwis
What i know it is for:
1- It is For Convert Asm to C++ without WINAPI.
2- Its Used for most time,to protect a Pointer or Multiple Pointers with Bytes.
Example:
Nopping Way.
1- It is For Convert Asm to C++ without WINAPI.
2- Its Used for most time,to protect a Pointer or Multiple Pointers with Bytes.
Example:
Nopping Way.
Originally Posted by Zacherl
OMFG hahaha made my day 
@Death-Dev
VirtualProtect changes the memory protection as some memories are read only or execute only
if you want to overwrite some piece of code (e.g hooking, patching stuff etc)
you must call VirtualProtect to allow writing
for example try this code to write two nops in MessageBoxA API in a windows application:
Code:
FARPROC MessageBoxA_Addr = GetProcAddress(GetModuleHandleA("user32.dll"), "MessageBoxA");
*(WORD*)(MessageBoxA_Addr = 0x9090; // error, memory protection is PAGE_EXECUTE only!
Code:
DWORD dwOld; VirtualProtect(MessageBoxA_Addr, 2, PAGE_EXECUTE_READWRITE, &dwOld);//Allow read, write, execute access for first 2 bytes *(WORD*)(MessageBoxA_Addr = 0x9090; //will not make error VirtuallProtect(MessageBoxA_Addr, 2, dwOld, &dwOld); //restore old protection
hope i helped
someone correct me if i said something wrong
Originally Posted by giniyat101
wtf you kidding?
same here
@Death-Dev
VirtualProtect changes the memory protection as some memories are read only or execute only
if you want to overwrite some piece of code (e.g hooking, patching stuff etc)
you must call VirtualProtect to allow writing
for example try this code to write two nops in MessageBoxA API in a windows application:
solution:
sorry for my bad english
hope i helped
someone correct me if i said something wrong
same here
@Death-Dev
VirtualProtect changes the memory protection as some memories are read only or execute only
if you want to overwrite some piece of code (e.g hooking, patching stuff etc)
you must call VirtualProtect to allow writing
for example try this code to write two nops in MessageBoxA API in a windows application:
Code:
FARPROC MessageBoxA_Addr = GetProcAddress(GetModuleHandleA("user32.dll"), "MessageBoxA");
*(WORD*)(MessageBoxA_Addr = 0x9090; // error, memory protection is PAGE_EXECUTE only!
Code:
DWORD dwOld; VirtualProtect(MessageBoxA_Addr, 2, PAGE_EXECUTE_READWRITE, &dwOld);//Allow read, write, execute access for first 2 bytes *(WORD*)(MessageBoxA_Addr = 0x9090; //will not make error VirtuallProtect(MessageBoxA_Addr, 2, dwOld, &dwOld); //restore old protection
hope i helped
someone correct me if i said something wrong
Sorry if i am wrong
Originally Posted by darlwis
It is For Convert Asm to C++ without WINAPI.
Originally Posted by Zacherl
OMFG hahaha made my day
I think this is a VirtualProtect code, I am not sure
you gonna need to update the addys 
(Note: This is leeched, so don`t ask me how to update because IDK how
but I am not using it anymore)
you gonna need to update the addys (Note: This is leeched, so don`t ask me how to update because IDK how
but I am not using it anymore)Code:
BYTE nop = 0x90; DWORD d, ds; VirtualProtect((LPVOID)(CShell+0x85723), 17, PAGE_EXECUTE_READWRITE, &d); for (int i=0; i<17;i++) memcpy((LPVOID)(CShell+0x85723+i), &nop, 1); VirtualProtect((LPVOID)(CShell+0x85723), 17, d, &ds);
It sets the protection of memory.
In xmen's example, 17 Bytes are getting protected, that these 17 Bytes are readable, writable and that they can get executed.
Then some NOPs are being copied into these 17 Bytes and then the protection is set to the protection before the first call of VirtualProtect.
@darlwis
What are you talking about?
In xmen's example, 17 Bytes are getting protected, that these 17 Bytes are readable, writable and that they can get executed.
Then some NOPs are being copied into these 17 Bytes and then the protection is set to the protection before the first call of VirtualProtect.
@darlwis
What are you talking about?
