AutoHotkey Community

[_Guest_]

I am using program to decompile my scripts and cannot figure out how to make protection from decompiling. I dont know how to make custom compiler. I was trying to make my own obfuscrator and did not understand how to compile custom ahk, it made a lot of errors during compilation. I was trying to find replacement to upx.exe file and failed. I was trying to work with hex editor, and change version of autohotkey in exe-file. Exe files seems digitally signed and all of them did not work after modification. I am not a hacker, I could not understand how to repair them. I was trying to use passwords with german letters, as suggested about year ago, my decompiler can eat them. May be somebody can help and suggest some protection from well known decompiler which produce log file like this?

[Guest]

Ultimately, it is impossible to prevent decompiling. After all is said and done, the script will be in memory and can be captured. There have been many discussions on this topic. If your are interested search the forums.

Search Tips:
method 1 (forum), method 2 (site), method 3 (Google)

[_Guest_]

One thing if script extracted from memory, this is unavoidable. But this is not easy task. You cannot do this without skills and practice. And another thing is that compilation can be decompiled by direct method. And you need nothing to know to repeat this. Discussion here was focused on protection of the script in memory, and took not so much attention to direct decompiling.

[_Guest_]

[Lexikos]

In my experience the password can be bypassed entirely. By "bypassed" I mean it isn't cracked, it just isn't required to decompile the script. Any discussion about cracking passwords therefore becomes pointless.

[Clash]

my friend can crack them in less than 15 minutes
_________________

[Lexikos]