Linking C++ DLL and Visual Basic Executable Together
Posts 16–30 of 42 · Page 2 of 3
Originally Posted by Mayion
As I've said, on injection have the Dll to check if your loader process is on or not. - In the code of your dll itself.
> If loader process = true, execute the rest of the code, if not, show up a message saying injection failed.
This is a good idea. But I found something about IPC (Inter-process communication) on Google. I will use this for a short time, I would also like to learn more about IPC if anyone wills to teach?
Originally Posted by Raydenman
O really? pt.2
This was already served, but I still can't understand why you shouldn't do it already from vb.net ...
Do what in .NET? His Dll is coded in C++ and wants ONLY his loader to inject it.
What's the point of doing it from the loader itself?
> Only loader.exe can inject .dll, so if I cracked his loader.exe and got the .dll, it wouldn't inject.
He makes the loader on VB.NET.
The loader must CHECK if the game is opened.
Originally Posted by Mayion
Do what in .NET? His Dll is coded in C++ and wants ONLY his loader to inject it.
What's the point of doing it from the loader itself?
> Only loader.exe can inject .dll, so if I cracked his loader.exe and got the .dll, it wouldn't inject.
Do you understand?
Is it so hard to do the check from VB.NET?
Why to complicate deh life?
- - - Updated - - -
Originally Posted by buxkaizhe
This is a good idea. But I found something about IPC (Inter-process communication) on Google. I will use this for a short time, I would also like to learn more about IPC if anyone wills to teach?
In .net managed classes there is only a solution to IPC: remoting.
Originally Posted by Mayion
As I've said, on injection have the Dll to check if your loader process is on or not. - In the code of your dll itself.
> If loader process = true, execute the rest of the code, if not, show up a message saying injection failed.
Well no. Anyone can make a fake process with the same name as the loader's one.
IPC is kinda the right solution. Very clever. You can set a window hook to intercept window messages inside the process inside which the DLL is loaded. The loader will then send window messages to the process to confirm that the DLL has been loaded from its rightful owner.
Again this is very easily detectable (if you wish to crack the loader) so this + encrypting the DLL will do the job pretty fine.
I guess I should use FindWindow 1st as I have no knowledge about IPC. Im a newbie.
Can you help me on providing some source code or example on IPC?
Thanks.
Originally Posted by ლ(ಠ_ಠლ)
IPC is kinda the right solution.
This is not true.
Originally Posted by ლ(ಠ_ಠლ)
You Can Set A Window Hook To Intercept Window Messages Inside The Process Inside Which The DLL Is Loaded.
Can you be more specific?
That will be possible just with unmanaged code.
Windows hooks? mmm...
Originally Posted by ლ(ಠ_ಠლ)
So This + Encrypting The DLL Will Do The Job Pretty Fine.
Why should you encrypt it? ...
Originally Posted by Raydenman
This is not true.
Can you be more specific?
That will be possible just with unmanaged code.
Windows hooks? mmm...
I know what are windows hooks, but this isn't the case.
Originally Posted by Raydenman
Ah, then it's useless and no-sensed
I know what are windows hooks, but this isn't the case.
So what would you suggest ?
Originally Posted by ლ(ಠ_ಠლ)
So what would you suggest ?
Nothing to suggest. He didn't ask that
Originally Posted by Raydenman
Nothing to suggest. He didn't ask that
So what did he ask ?
Originally Posted by ლ(ಠ_ಠლ)
So what did he ask ?
For sure, not how to .. "Set a Window Hook to Intercept window messages", am I right?
Originally Posted by Raydenman
For sure, not how to .. "Set a Window Hook to Intercept window messages", am I right?
Well he asked about IPC, which itself can be done via windows messages.
Originally Posted by ლ(ಠ_ಠლ)
which itself can be done via windows messages.
"IPC is kinda the right solution." No.
Anyway, no ...
For that you must get an unique message number using RegisterWindowsMessage; Then broadcast on this number (make all recipients reply/send back their hWnds); then use SendMessage.
Originally Posted by Raydenman
"IPC is kinda the right solution." No.
Anyway, no ...
For that you must get an unique message number using RegisterWindowsMessage; Then broadcast on this number (make all recipients reply/send back their hWnds); then use SendMessage.