[Release] Tool to prevent decompilation of your Autoit-Code

Shadow,
I found a bug, but I cant give the sample code, so I dont know if this can help or not.

One of my script consist of around 5000 lines, after obfuscated it's around 15000 lines.

When running the protected obfuscated script, it will error:

Line 4 (file "c:\myscript.exe"):

Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded.

The compiled obfuscated script is not error, so the error must be in the protector.exe side

edit: somehow, i dont think this bug happen with the older version, but I cant test it because as you know, (some) obfuscator use FileInstall

Hm ich glaube ich mache etwas falsch. Ich soll die Exec. und die Safe.exe in das Script Verzeichnes machen, aber er behauptet, dass es nicht funktioniert.
Win8
Als Admin gestartet

Hast du die datei auch umbenannt ? sind alle dateien im selben verzeichnis ?

Jop alles so wie es soll mehrmals überprüft.

Ich hab auch win 8 . Bei mir gehts .
Daraus lässt sich ganz einfach die lösung ziehen :
Du machst was falsch :p

language very fragile, applies only to the macros

Ist es möglich der gesicherten Exe ein Icon zuzuweisen so wie bei der ungesicherten Variante?

Quote:

Originally Posted by Rolle Ist es möglich der gesicherten Exe ein Icon zuzuweisen so wie bei der ungesicherten Variante?

Use Res Hacker.
I found a mate who helps me developing the exe and making it more secure. We will release new version when I am back. This will be on sunday/monday.

Then also some bugs will have been fixed.

Quote:

Originally Posted by Shadow992 Use Res Hacker.

Merci =)

Getestet, crasht leider nonstop :/
Der Teil der Safe.exe funktioniert nach einigen Tests wenn die Alibi-Dateien nicht zu komplex sind. Die SecureAu3.exe gibt leider sofort "error: 1" zurueck.

AntiVir ist deaktiviert, Win7 64bit (Skript auf x86 kompiliert), kein UPX, alle Dateien haben Adminrechte

Quote:

Originally Posted by Shadow992 Use Res Hacker. I found a mate who helps me developing the exe and making it more secure. We will release new version when I am back. This will be on sunday/monday. Then also some bugs will have been fixed.

Shadow,
May I know, what bugs you're talking about?

Quote:

Originally Posted by link [Only registered and activated users can see links. Click Here To Register...]

I like the above picture so much and so I posted my protected files below. Link decompiler(current version as of testing) dont work on these 2 files below.

Using a special autoit compiler and a packer(you can called it a combo packer, both tools are freeware). Please note this method isnt useful at all cause antivirus will automatically delete this exe file.
Test1.rar

Using normal autoit setting compiler and another software/tool(this software/tool is freeware). Please note this method isnt safe at all because of this software/tool I use, and some antivirus(not all) will trigger autoit false alarm.
Test2.rar

Both methods/tools/software/utility will not be publish since its using more than 1 year old packer/tool/software available on the internet. And as of now, its still available for download.

PS: both methods works against another 2 autoit decompilers(using default setting of course) that I know of, available on the internet too.

This is just for fun. No hard feelings.

Both methods exe can be unpack easily by the expert(Link included, thats why methods will not be share).

But.. I can tell how I first started protecting autoit in the beginning, autoit obfuscator(official version, I was abit annoy/shock, it was so easy to deobfuscate it with a decompiler(I think cw2k version)) then..., it was very easy, I wrapped it with winrar/sfx...(yeah its abit silly but thats how it all got started), then things become abit more completed...I match different tools/software/utilities into my protection...
So now, the method/concept/procedure are basically still the same for me except the tools/software/utilities used are different.

PS: Sorry was sleepy the other day, I redo everything and reupload.
Please note, antivirus alert will be trigger, test it out in protected system if possible.

#Updated
- Made protection better (Thanks to Jeoni)
- Changed some things and made them more stable (Thanks to Jeoni)
- Removed some bugs (Thanks to Jeoni)

Jeoni will work even more with me at this protector and will try to make it even harder to decompile AutoIt.

Quote:

Originally Posted by DuguWudi I like the above picture so much and so I posted mine below Source code Code: MsgBox(4096, "Test", "This box will time out in 10 seconds", 10) Using normal autoit setting compiler and Link decompiler [Only registered and activated users can see links. Click Here To Register...] Using a special autoit compiler and a packer(you can called it a combo packer, both tools are freeware) and Link decompiler. Please note this method isnt useful at all cause antivirus will automatically delete this exe file. [Only registered and activated users can see links. Click Here To Register...] Using normal autoit setting compiler and another software/tool(this software/tool is freeware) and Link decompiler. Please note this method isnt safe at all because of this software/tool I use, and some antivirus(not all) will trigger autoit false alarm. [Only registered and activated users can see links. Click Here To Register...] Both methods/tools/software/utility will not be publish since its using more than 1 year old packer/tool/software available on the internet. And as of now, its still available for download. PS: both methods works against another 2 autoit decompilers(using default setting of course) available on the internet too. This is just for fun. No hard feelings. Both methods exe can be unpack easily by the expert(Link included, thats why methods will not be share). But.. I can tell how I first started protecting autoit in the beginning, autoit obfuscator(official version, I was abit annoy/shock, it was so easy to deobfuscate it with a decompiler(I think cw2k version)) then..., it was very easy, I wrapped it with winrar/sfx...(yeah its abit silly but thats how it all got started), then things become abit more completed...I match different tools/software/utilities into my protection... So now, the method/concept/procedure are basically still the same for me except the tools/software/utilities used are different.

This is not the sourcecode. xD
And your links are broken, too.

Shadow,
This latest version produce 2 file: _safe.exe and _secure.exe
_secure.exe has bigger file size.
What is the different between them?

_secure.exe has this error, while _safe.exe not:

-------
Shadow,
I found a bug, but I cant give the sample code, so I dont know if this can help or not.

One of my script consist of around 5000 lines, after obfuscated it's around 15000 lines.

When running the protected obfuscated script, it will error:

Line 4 (file "c:\myscript.exe"):

Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded.

The compiled obfuscated script is not error, so the error must be in the protector.exe side

edit: somehow, i dont think this bug happen with the older version, but I cant test it because as you know, (some) obfuscator use FileInstall
------------

Quote:

Originally Posted by superman8855 Shadow, This latest version produce 2 file: _safe.exe and _secure.exe _secure.exe has bigger file size. What is the different between them? _secure.exe has this error, while _safe.exe not: ------- Shadow, I found a bug, but I cant give the sample code, so I dont know if this can help or not. One of my script consist of around 5000 lines, after obfuscated it's around 15000 lines. When running the protected obfuscated script, it will error: Line 4 (file "c:\myscript.exe"): Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded. The compiled obfuscated script is not error, so the error must be in the protector.exe side edit: somehow, i dont think this bug happen with the older version, but I cant test it because as you know, (some) obfuscator use FileInstall ------------

I think I forgot to delete _safe.exe just use _secure.exe.
This error may occur because FileInstall may not work perfect. :/
Just use a script and do following:
And try it without obfuscator, if it will work then it must be because of FileInstall.
If it is because of FileInstall, did you update AutoIt?
If yes this may be the problem.