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

Shadow992,
Few questions:
1. Are you sure it support CUI directive now? Because I just tested it and seems it's still not.

2. Is this version not decompileable by previous manual decompilation method by link?
(except he found a new method to do it :p)

3. Why not including FileVersion and Copyright directive support?

Thank you so much for this amazing software :)

Quote:

Originally Posted by superman8855 Shadow992, Few questions: 1. Are you sure it support CUI directive now? Because I just tested it and seems it's still not. 2. Is this version not decompileable by previous manual decompilation method by link? (except he found a new method to do it :p) 3. Why not including FileVersion and Copyright directive support? Thank you so much for this amazing software :)

1. Pretty sure yes, i tested it and it worked.
You can test it for me by debugging what were passed as arguments and what not. You can even send me your script (or just an example script where it does not work) so I can have a look by myself.

2. I think it will be for sure possible for him to decompile it by hand but I also hope he will have big problems adding this to his program. :D
He even did not release his new decompiler so I were not able to test it and just had to think about some scenarios how he could have cracked it.

3. This seems to be a little more work thats why I am going to add that later on.

i try this, but it tell me that exe must be not upx packed. But in the header of script i put #AutoIt3Wrapper_UseUpx=n

About CUI, I haven't test with any arguments, but if it works (if it honor the CUI directive), it should not open another command prompt to execute the compiled script.

Example:

This is the script:

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_UseUpx=n
#AutoIt3Wrapper_Change2CUI=y
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****

ConsoleWrite("This is a CUI script" & @CRLF)

If not protected (if it honor the CUI directive):

c:\>cui
This is a CUI script

c:\>

This is the result of the protected one:

c:\>cui_secure

c:\>

If doesn't display anything because when it run it open another command prompt window, execute it there and then close the window. For this I said it doesn't honor the CUI directive :)

Also I want to report small bug:

Script you want to make secure --> c:\myfolder\myscript.exe
Output --> c:\myfolder\result\myscript.exe

c:\myfolder\result\ folder is exist.

It will said "Something went wrong this normally only occurs ..."
So instead it create it result file at c:\myfolder\result\myscript.exe
it will create it at c:\myfolder\myscript.exe
(overwrite the old/input file)

Quote:

Originally Posted by fuso98 i try this, but it tell me that exe must be not upx packed. But in the header of script i put #AutoIt3Wrapper_UseUpx=n

The header said that, but do you recompile it after you add the directive?

About the UPX, i just notice that Shadow assume if your compiled script is less than 550Kbps in size, it assume it's packed with UPX

Quote:

Originally Posted by superman8855 About the UPX, i just notice that Shadow assume if your compiled script is less than 550Kbps in size, it assume it's packed with UPX

Yes if script is less 550 its packed because the original AutoIt-Interpret have got around 600kB. ;)

my exe is abount 440 kb.. so i must make it more big??

Quote:

Originally Posted by fuso98 my exe is abount 440 kb.. so i must make it more big??

Its not abot the size but about special characters my programs are looking for and if the exes are packed the characters are missing or encrypted.

Sometimes even if you add the directives like you did autoit compiles with upx. To totally avoid this try the following:

Right click on your .au3 file and select "compile with options" then you are able to disable upx in the checkbox. ;)

Hi Shadow,
Today I compile one of my CUI script and protect it using the anti decompile tool. I forget that it will need to call some externals command through loop. The result is it display so many command prompt window.

Hope we can have the protector with CUI support soon.

Thanks! :)

Quote:

Originally Posted by fuso98 my exe is abount 440 kb.. so i must make it more big??

What is your AutoIT version? without UPX packed, it should be more than 600KB. Even 1 line compiled script will be more than 600KB

Quote:

Originally Posted by superman8855 Hi Shadow, Today I compile one of my CUI script and protect it using the anti decompile tool. I forget that it will need to call some externals command through loop. The result is it display so many command prompt window. Hope we can have the protector with CUI support soon. Thanks! :) What is your AutoIT version? without UPX packed, it should be more than 600KB. Even 1 line compiled script will be more than 600KB

Hmm for me CUI is working?
Something must be different.
I tested with following script:
Worked perfect, output:
"This is a CUI script"

Quote:

Originally Posted by Shadow992 Hmm for me CUI is working? Something must be different. I tested with following script: PHP Code: #Region ;**** Directives created by AutoIt3Wrapper_GUI ****  #AutoIt3Wrapper_UseUpx=n  #AutoIt3Wrapper_Change2CUI=y  #EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****  ConsoleWrite("This is a CUI script" & @CRLF)  Sleep(22222)  Worked perfect, output: "This is a CUI script"

No, it doesn't.

Not because it display "This is a CUI script" then it worked perfect :)

Run it this way:

1. Open a command prompt window (Start | Run, type "cmd")
2. cd\WhereTheCUICompiledScriptAre
3. cui_secure.exe

If it work perfect it will display "This is a CUI script" on that same command prompt window.

It is NOT, because it will automatic open another command prompt window just to display "This is a CUI script", sleep for a while, close that command prompt window and back to the "original" command prompt window.

Compare with the original cui.exe: it will NOT open another command prompt window.

Open another command prompt window is doesn't a problem if you dont call another cui application from the script (@comspec & ' /c ') and then ConsoleWrite again, otherwise it will open another command prompt upon execution. If you loop hundreads of time calling those external CUI application, it will display hundreads of command prompt window where the unprotected cui.exe doesn't.

Quote:

Originally Posted by superman8855 No, it doesn't. Not because it display "This is a CUI script" then it worked perfect :) Run it this way: 1. Open a command prompt window (Start | Run, type "cmd") 2. cd\WhereTheCUICompiledScriptAre 3. cui_secure.exe If it work perfect it will display "This is a CUI script" on that same command prompt window. It is NOT, because it will automatic open another command prompt window just to display "This is a CUI script", sleep for a while, close that command prompt window and back to the "original" command prompt window. Compare with the original cui.exe: it will NOT open another command prompt window. Open another command prompt window is doesn't a problem if you dont call another cui application from the script (@comspec & ' /c ') and then ConsoleWrite again, otherwise it will open another command prompt upon execution. If you loop hundreads of time calling those external CUI application, it will display hundreads of command prompt window where the unprotected cui.exe doesn't.

The only way to do this is the following:
You must hide the created AutoIt-Console and it will still create 1 Console for every AutoIt-Script but they will all be summed up in 1 Console this also means Commands may not work.

So the only things that are doable:
- Showing what were written in the started autoit-console
- Write to started autoit console

What is not able:
- Start another AutoIt-Process from your autoit file and read his input/output (maybe its possible because executed script may write to same window as started script_secure.exe)
- But it is for sure not possible to do all the things in the created autoit-console we MUST create ONE new console (the autoit console which is automatically created when running cui at the moment) so if we are going to try that you would have to hide the cui console of autoit.

Shall we try it or is this not the way you want to have?
There is at the moment no other way except using send/controlsend in autoit.

Edit:
I will just try it maybe its working the way we want to. ;)

Edit2:
Ok seems harder to be as thought. I think this will not be implemented that fast.
Dont know if it ever will be implemented.

Quote:

Originally Posted by Shadow992 Edit: I will just try it maybe its working the way we want to. ;) Edit2: Ok seems harder to be as thought. I think this will not be implemented that fast. Dont know if it ever will be implemented.

Thanks, Dude! :)

I believe you can :handsdown:

btw, when protecting (when the protecter.exe run), does it call aut2exe.exe to compile the script? It should, isn't it? If yes, shouldn't we can ask aut2exe.exe to compile it as a CUI application?

Quote:

Originally Posted by superman8855 Thanks, Dude! :) I believe you can :handsdown: btw, when protecting (when the protecter.exe run), does it call aut2exe.exe to compile the script? It should, isn't it? If yes, shouldn't we can ask aut2exe.exe to compile it as a CUI application?

Nope it is not calling Aut2exe. ;)

Edit:
Finally its working. I just have to remove these false positive Viruswarnings again and add a Checkbox to Protecter.au3 and then its ready. But before release I want to make also some other things to make decompiling harder.

Quote:

Originally Posted by Shadow992 Nope it is not calling Aut2exe. ;) Edit: Finally its working. I just have to remove these false positive Viruswarnings again and add a Checkbox to Protecter.au3 and then its ready. But before release I want to make also some other things to make decompiling harder.

Wow, great :handsdown:

:pimp:

:pimp:

Anyway, If it possible, please maintain the original compiled script icon, fileversion and copyright information. If that is not possible, please let user define new icon file and those information upon protecting through the protector GUI.

Quote:

Originally Posted by superman8855 Wow, great :handsdown: :pimp: :pimp: Anyway, If it possible, please maintain the original compiled script icon, fileversion and copyright information. If that is not possible, please let user define new icon file and those information upon protecting through the protector GUI.

I will add this in next version, too.