[NaS]

Quote:

Originally Posted by VeryTallMidget Most of them will manipulate memory or is there some other way ? When i worked on my server, i created a hack to quickly teleport to desired locations, it was done by reading players position out from sa:mp memory to save positions and writing memory to teleport savfed positiond read from ini file. Samp uses dynamic memory for player pos, so it requires offsets to read/write effectivly. dll is called from program by dll's name, so changing only that will end up with error, sooner or later, sometimes later if the dll is dynamic not static that is read at start. Код: function Out32(PortAdr: word; Data: byte): byte; stdcall; external 'inpout32.dll'; Just some example from the program code I used to read and write LPT port data to control step-motor, here the inpout32.dll is called.

There are multiple methods to hook foreign DLLs or actually any file.

- Mapping DLLs using WinHooks or other more advanced programs
- Modifying your DLL to also load mine
- Modify your code to load my DLL, which is basically what you did with the SAMP Player Pos just a tiny bit more advanced...

You don't even need an ASI loader for ASIs btw. Just inject an asi (which is literally a renamed DLL).

Anyway this is by far not the only possible attack or circumvention I could think of. I'm just trying to say that you NEED to secure your Launcher efficiently against all kind of things, even if you are sure that noone will inject a DLL.
What about network layer? What keeps me from replicating your code?