>> >>>It's a common technique to rely on the fact that exports from kernel32
>> >>>reside at the same address to use CreateRemoteThread calling LoadLibrary
>> >>>for remote code injection (this is not what Vitaliy's App is doing here
>> >>>but the assertions are the same).
>> >>It's hard to implem
Saturday, August 6, 2005, 11:24:05 PM, Mike McCormack wrote:
>> app1.exe: GetProcAddress(mKernel32, "LoadLibraryA") returns 0x404FCBCC
>> app2.exe: GetProcAddress(mKernel32, "LoadLibraryA") returns 0x404FFBCC
>> Is there are any reason why this is happening? Any ways to fix this?
> Under Windows
