Printable View
I'd like to protect my EXE's memory from being read, written, etc. I'm pretty sure that this goes down to kernel level and i'd haveto compile a .sys and reference from that, but please correct me if im wrong :) And if i dont haveto go down to kernel level, then what api's would i use? :eek2: neways thanks for any input :wave:
Read by Whom????? Windows already protects your exe's memory. Why do you want to attempt this?
I'm not quite sure, but i think that "Private" makes your reserved memory available only to you. But that's just an assumption ;)
edit: Try to reach a "Private" sub/function directly from another module. When you'll do that... maybe you'll be a step closer ;)
@randem: memory editors (game cheaters)
@gavio: could you explain further?
Look at my edit. Maybe it's just me... maybe i don't know how to programme, but... i can't reach a private variable/sub/function (anything that is private) from another module. But that's in the same EXE!! I can't even start to think about from another EXE.
gavio,
That's just for the VB compiler and subsystem. It has no effect on the OS.
You can't hide memory, you can only encrypt it.
yet again, i said protect, not hide ;) and you could rootkit to hide the process, but they could still get the hook via window/pID. thats why im pretty sure you'd haveto drop down to kernel level with a .sys file and protect it from there... idunno though
They could go down to the kernel level and read it anyway. And that's only for data generated during runtime. Anything statically stored in the exe is always available on disk.
yes, they could, but most people just use the utilities available. they have no clue how to make their own. there is nothing important stored into the exe itself. thnk you for your input though, does anyone else ahave any
That's true. Nothing important is stored in exe, looking from the data point of view. But looking from algorithm point of view, well, that's just another story ;)
dingdingding we have a winner lol :)
even if i did an algorithm to hide the values, it could be reverse engineered out x_x
thats why i need to block the functions overall... and im not sure what todo...
huh... maybe if you make a .ini file and put it in some weird place.
c:\program files\fake program name\1548\some fake file\somewhere else\something\else\oh no\and here we go\settings.ini