![]() |
|
#5
|
|||
|
|||
|
Hello,
Quote:
Damn, if I'm programming a CRC check I would do it both on file and memory ! So ok, if it's done only on file, you're right, please forgive me.As you're creating yourself the process, retrieving the DLL base is easy with this API: EnumProcessModules. Then you can extract some information with those API's: -GetModuleBaseName -GetModuleFileName -GetModuleInformation There's also another by getting the PEB of the process, and reading some fields from it. In fact interesting fields for your case are located in the PEB_LDR_DATA struct which is a currently holding information about Loaded modules. This is a far complex way to retrieve the same informations. A problem comes when the DLL isn't loaded in the program and will be loaded later with a 'LoadLibrary'. Well, one possibility : -Hooking the LoadLibrary function from the program and then performing the above trick. Maybe threre are some other ways when the DLL is not loaded when launching the program but I can't see them... I'll try to code something, try also on your side. Regards, Neitsa. |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Loader and Patch Dll file in C# | mcr4ck | Source Code | 0 | 06-19-2022 23:59 |
| Creating a Loader for DotNet Apps? | bball0002 | General Discussion | 2 | 09-24-2009 22:06 |