iPromise Grandmaster Cheater
Reputation: -1
Joined: 27 Jun 2009 Posts: 529 Location: Canada
|
Posted: Thu Jul 18, 2013 10:12 pm Post subject: Locating DLL Entrypoints with a driver |
|
|
hey guys,
I have two questions that I hope can be answered. My first question is with regards to DLL encryptors. Once you've encrypted a DLL, all the signatures change until the DLL is loaded; is that correct?
For example, lets say you compiled a DLL with this variable:
| Code: |
BYTE Signature [] = { 0xFF, 0xFF, 0xFF, 0xAA };
|
If you view that DLL with a disassembler, you can find that signature in the hex viewer.
But after you've encrypted it, you won't find that signature, not until its been loaded up and the encryptor decrypts itself, correct?
My second question is rather straightforward. How can we determine all the modules loaded within an application in a driver. I'm personally looking for one module, and ofcourse I don't have the tlhelp32 library to help me so I was wondering if there were any techniques or references to kernel tlhelp32 functions of some sort.
I need to find the entry-point of the module so I can do a signature check for my public key of my driver to ensure that the library loaded isn't foreign.
thanks.
|
|