Anti Memory dump ?

[Vivi]

Hey dear community,

i write alot of programs that i sell.

i coded a sucessfull license system but sadly i have no protection against memory dumps.

 

i already tried playing with "memory.au3" but failed at it.

#include <WinAPI.au3>
#include <Memory.au3>
#include <NoMadMemory.au3>
$Mem_Open = _MemoryOpen(@AutoItPID)
$baseAddress = _WinAPI_GetModuleHandle(0)
_MemVirtualAlloc($Mem_Open, BinaryLen($Mem_Open), $MEM_COMMIT, $PAGE_GUARD)

 

anyone has a idea how i can call use page guard ?

 

Thanks

[Mobius]

Many products have tried but all fail in this regard, particularly in situations where someone knows what they are doing.

Sorry Vivi but that's just the way of it.

Vlad

[Vivi]

Many products have tried but all fail in this regard, particularly in situations where someone knows what they are doing.

Sorry Vivi but that's just the way of it.

Vlad

i already found a method on how to stop decompilers do there job.

bypassed sniffers and co

 

are you sure there is no way to use page guard's or any other method to prevent memory dumps ?

[JohnOne]

i already found a method on how to stop decompilers do there job.

No, no you have not.

i have no protection against memory dumps.

There's the evidence.

[Mobius]

Who's talking about decompilation?

(despite you bold and incorrect assumption regarding this long term)

We (or rather you) are talking about memory, the weakpoint of every application to date.

Am I saying implementing page guard is Impossible? No not really, and hopefully someone will at least help you do this much to put you in a false sense of security mindset short term so you can continue developing your content without worrying where the holy grail has been stashed.

 

[Vivi]

No, no you have not.

i have no protection against memory dumps.

There's the evidence.

add "#end region" in the first line.

 

 

Edited October 28, 2015 by Vivi

[JohnOne]

That is not the only decompiler, and it will not protect a script against decompilation.

If it did, you would not be here looking for a solution.

Plenty get the script from memory at runtime. you cannot stop that.

[Mobius]

@Vivi please remove the name of the decompiler in post 6 and use something like "memory based or focused decompiler".

 

As JohnOne has stated it isn't the only one these days so there is no real need to reference any single one by name.

 

Edited October 27, 2015 by Mobius

[Melba23]

Hi,

This thread has now gone beyond the limits - locked.

M23