How to prevent decompile script

[Jos]

So the management (yourself included) has to watch for, and head off, such threads.

Looking forward to the next management-team meeting Jon will call.

[Melba23]

Jos,

Which bar was it again?

M23

[firsttimer]

You can try as a variant, too.

br,

UEZ

AutoIt3Camo alone by itself isnt secure anymore, but you could archive it with a winrar/winzip and made into a selfextracter when run will extract to a temp folder(or any folder name you specify) to run your compiled exe file. This method add a little bit of security. You could search selfextractor maker in softpedia, theres alot of freeware there.

(This is just a simple example of how to protect your compiled exe, you could create your own method.)

Alot of people come out with their own private protection methods, then they release their autoit software as freeware/shareware/etc.

Private methods means these methods are never publish/share anywhere, which give them a little bit more security(but not totally secure, for those diehard who spend their time...), its better than nothing.

[Mobius]

AutoIt3Camo has never been considered enough protection on its own.

The rules of engagement have not changed, and as always every programs weakness is its own memory space.

Lets say theoretically someone were to attack your AutoIt exe from memory, if your exe used a type of softarmor that did not execute the payload in its own memory space, such an attack may be slightly less effective. Oh and bunging the exe in an sfx will work simply because the initial executable interrogated is not the target, which itself is being executed as another process.

Vlad

Edited April 3, 2013 by Mobius