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

[-STORM-]

Originally Posted by superman8855

Is it possible to maintain the old icon and file properties after protect it?

You can use Reshacker for that purpose.

[superman8855]

@STORM: thanks
I know about Resources Hacker, but if we have many exe we want to protect and those exe files updated regulary, it will spend time.

In the protecter.exe, it will be great if before press "Start" button we can choose the ico file and at the same time can define FileVersion and Copyright information.
So if it's not possible to retain those information from the old exe file, is it possible to add 3 more inputbox to protecter.exe?

1 for ico file (#AutoIt3Wrapper_Icon)
1 for FileVersion (#AutoIt3Wrapper_Res_Fileversion)
1 for Copyright (#AutoIt3Wrapper_Res_LegalCopyright)

I just try ResHacker, it can change icon on the protected file, but could not change FileVersion and Copyright

Seems like the protecter.exe doesn't honor command line (CUI) directive.

I have this on my original code:

#AutoIt3Wrapper_Change2CUI=y

But after protected, it open a new command prompt window instead of running it from current command prompt window

[Shadow992]

Originally Posted by superman8855

@STORM: thanks
I know about Resources Hacker, but if we have many exe we want to protect and those exe files updated regulary, it will spend time.

In the protecter.exe, it will be great if before press "Start" button we can choose the ico file and at the same time can define FileVersion and Copyright information.
So if it's not possible to retain those information from the old exe file, is it possible to add 3 more inputbox to protecter.exe?

1 for ico file (#AutoIt3Wrapper_Icon)
1 for FileVersion (#AutoIt3Wrapper_Res_Fileversion)
1 for Copyright (#AutoIt3Wrapper_Res_LegalCopyright)

I just try ResHacker, it can change icon on the protected file, but could not change FileVersion and Copyright

Will have a look at it, yes.
But at first I am working at a more secure version, which hopefully also makes it much harder for link who at the moment cracked my protection (but just by hand and he even did not write any program that could decompile it, but still if you are going to share some vulnerable texts/scripts wait for my next version).

[link]

doch, doch, hatte es auch direkt in Exe2Aut eingebaut, aber noch nicht hochgeladen :P

[Shadow992]

Originally Posted by link

doch, doch, hatte es auch direkt in Exe2Aut eingebaut, aber noch nicht hochgeladen :P

Penner xD

[superman8855]

Originally Posted by Shadow992

Will have a look at it, yes.
But at first I am working at a more secure version, which hopefully also makes it much harder for link who at the moment cracked my protection (but just by hand and he even did not write any program that could decompile it, but still if you are going to share some vulnerable texts/scripts wait for my next version).

Thank you very much, Shadow992

Cant wait for your next version

Current protector.exe seems doesn't honor any directives, including command line (CUI) directive (#AutoIt3Wrapper_Change2CUI). It will be great if on the next version, it does support directives.

Thanks again!

[Shadow992]

Originally Posted by superman8855

Thank you very much, Shadow992

Cant wait for your next version

Current protector.exe seems doesn't honor any directives, including command line (CUI) directive (#AutoIt3Wrapper_Change2CUI). It will be great if on the next version, it does support directives.

Thanks again!

Even dont know what these directives are for but i think it will be very hard to implement this.

[superman8855]

Originally Posted by Shadow992

Even dont know what these directives are for but i think it will be very hard to implement this.

This directive (#AutoIt3Wrapper_Change2CUI) is pretty common, it tell this script is a command line application, not GUI, so when we run it from command prompt, any output (including ConsoleWrite) will written to current command prompt (dos) window, it doesn't open a new window for it.

In the protecer.exe GUI, you might want to add a checkbox "Is a CUI script". If checked, then compile it with #AutoIt3Wrapper_Change2CUI=y

[Shadow992]

Originally Posted by superman8855

This directive (#AutoIt3Wrapper_Change2CUI) is pretty common, it tell this script is a command line application, not GUI, so when we run it from command prompt, any output (including ConsoleWrite) will written to current command prompt (dos) window, it doesn't open a new window for it.

In the protecer.exe GUI, you might want to add a checkbox "Is a CUI script". If checked, then compile it with #AutoIt3Wrapper_Change2CUI=y

Ok this is possible to add but i have to look how i could do this. But i will have added it for sure in next version.

[superman8855]

Originally Posted by Shadow992

Ok this is possible to add but i have to look how i could do this. But i will have added it for sure in next version.

Thanks, Shadow992!

[nockiro]

Danke Shadow992 für das nützliche Tool.
Ich habe leider auch das von FlutterShy auf Seite 2 beschriebene Design-Problem - nur unter Windows 7.
Ansonsten hätte ich nur noch einen Makel: Die Dateien, die mit FileInstall installiert werden sollen, haben keinen Inhalt, sprich sind 0-KB-Dateien.
Klasse Arbeit aber auf jeden Fall

Nockiro

[YatoDev]

Originally Posted by link

doch, doch, hatte es auch direkt in Exe2Aut eingebaut, aber noch nicht hochgeladen :P

Och ne -_- nicht automatisiert

ist doch blöd wenn das jeder decompilieren kann

Mal schauen ob shadow es schafft oder du

[Shadow992]

Originally Posted by nockiro

Danke Shadow992 für das nützliche Tool.
Ich habe leider auch das von FlutterShy auf Seite 2 beschriebene Design-Problem - nur unter Windows 7.
Ansonsten hätte ich nur noch einen Makel: Die Dateien, die mit FileInstall installiert werden sollen, haben keinen Inhalt, sprich sind 0-KB-Dateien.
Klasse Arbeit aber auf jeden Fall

Nockiro

Das Design-Problem scheint etwas Windows/AutoIt spezifisches zu sein das lässt sich leider nur schwer ändern sorry.

Das mit dem FileInstall hatte ich schon vermutet, werde mir das auch einmal anschaue ist nur die Frage ob ich das hinbekomme mal sehen.

Edit:
Erstmal steht jetzt aber Links Decompiler im Vordergrund und danach sehen wir weiter
Wird Zeit dass er mal die neue Datei hochlädt. Sonst kann ich sie ja net analysieren

[nockiro]

Originally Posted by Shadow992

Das Design-Problem scheint etwas Windows/AutoIt spezifisches zu sein das lässt sich leider nur schwer ändern sorry.

Das mit dem FileInstall hatte ich schon vermutet, werde mir das auch einmal anschaue ist nur die Frage ob ich das hinbekomme mal sehen.

Edit:
Erstmal steht jetzt aber Links Decompiler im Vordergrund und danach sehen wir weiter
Wird Zeit dass er mal die neue Datei hochlädt. Sonst kann ich sie ja net analysieren

Danke erstmal für die Antwort - sind ja alles keine so sehr großen Probleme.
Wichtig ist es ja wirklich erstmal, dass Links Decompiler nicht mehr hinterherkommt

Viel Glück noch,
nockiro

[Shadow992]

#Updated to 0.1.2
- Added more security things
- Added CUI support
- Added Win 7/Vista-Style-Support

Neue CrackMe ist auch da Link.