But I am wondering, does anyone know how to make a DLL (hack) work with a CERTAIN injector. Not the name, but a certain injector.
Thanks in advance!
P.S. Yes I have seen this done before, so I am wondering how
Yeah, you gotta code it. I guess it's out of your league now eh?
Ok guys. this guy is just asking a question, so I'm gonna give him a real answer.
If your looking to create an injector that will inject only your dll there are several ways to do this. The first way involves having to seperate files: A dll and an exe. You can either have the file search for the dll with a specified name in the same directory as the exe, but a popular way is having the .exe look for its own name. That way the .exe and the dll can be changed to different names which sometimes helps prolong a hacks life if ur making a public it allows people to uniquely name their hack to prevent string detection. However you can do this with a regular injector too.
For this reason I think the whole point of creating a custom injector is for added simplicity for your users. The less files they have to manipulate the better. So a way I used to do it is creating one exe and one dll, but adding the dll to the exe as a resources, then shipping the whole package as one file. I then proceeded to unload the DLL at runtime as a hidden file. (I didnt want to scare people by them seeing a mysterious dll flash up on their file window and then dissappear) Then I injected that DLL. However there are other ways to do it as well, such as memory mapped files, etc.
Trying doing a search for Tatnium injector. Its a great bit of source code to look at to learn from and to use. However make sure to give Azorbiz credit for his work, as a lot of time went into it.
Originally Posted by why06
Ok guys. this guy is just asking a question, so I'm gonna give him a real answer. *snip*
You're right. I was lazy. That's my morning mood ._.'
You mean so that your dll will only work if it's injected with a certain injector? Something I would do is allocate some memory, and write something specific to it (from the injector) then have the dll check that memory to make sure the injector injected.
~lilneo
Originally Posted by why06
