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

[Shadow992]

Originally Posted by superman8855

What if you release the next version that fix the working directory problem and another next version on FileInstall if FileInstall still need some time?

#Updated
- Fixed some problems with cmd
- Added a little bit more text to Protecter.exe/.au3

Now it should work with cmd and similiar.

[superman8855]

Originally Posted by Shadow992

#Updated
- Fixed some problems with cmd
- Added a little bit more text to Protecter.exe/.au3

Now it should work with cmd and similiar.

Many thanks, Shadow

I will try it and give you the report

[fuso98]

Originally Posted by Shadow992

#Updated
- Fixed some problems with cmd
- Added a little bit more text to Protecter.exe/.au3

Now it should work with cmd and similiar.

Now i can change .exe directory when i want?

[YatoDev]

Ich fände es interessant nochmal was von link (exe2aut) zu hören .

würde gerne mal wissen wie sicher die neue version ist .

[Shadow992]

Originally Posted by fuso98

Now i can change .exe directory when i want?

You can always change direcfory but not the name of exe.

Originally Posted by »FlutterShy™

Ich fände es interessant nochmal was von link (exe2aut) zu hören .

würde gerne mal wissen wie sicher die neue version ist .

Die neue Version wurde von link per Hand schon decompiliert, das war aber auch zu erwarten. Er will es noch in sein Programm einbauen und erst wenn er das Programm released hat kann ich wieder etwas dagegen machen.

Edit:
Und das hat er schon vor nen paar Wochen geschrieben aber irgendwie lädt er nix hoch. Wer mehr wissen will schaut in mein Profil bzw. in seines.

[MrSm!th]

- You can not rename the created file, if you do so the file will not work anymore. If you want to rename file you have to create a new file with my tool where you select a different name.

Ist imho ein ziemliches Problem. Du schränkst damit nicht nur den Entwickler, sondern sogar dessen Nutzer ein.
Das ist für Lib/Dev-Tool Entwickler eigentlich ein NoGo.

[superman8855]

My report as promised:
1. You forget to delete the temp file
2. the working folder issue is not fixed, it's now even worst.
The protected exe can be run from a window explorer with double click, but if run from a command prompt, even from it's folder, the general protection fault will appear. Like this:

c:\>myscript_secure.exe

it will display general protection fault. In previous version it will only gpf if run from another folder like this:

d:\>c:\myscript_secure.exe

[Shadow992]

Originally Posted by MrSm!th

Ist imho ein ziemliches Problem. Du schränkst damit nicht nur den Entwickler, sondern sogar dessen Nutzer ein.
Das ist für Lib/Dev-Tool Entwickler eigentlich ein NoGo.

Hmm, ich schau mich mal nach alternativen um.

Originally Posted by superman8855

My report as promised:
1. You forget to delete the temp file
2. the working folder issue is not fixed, it's now even worst.
The protected exe can be run from a window explorer with double click, but if run from a command prompt, even from it's folder, the general protection fault will appear. Like this:

c:\>myscript_secure.exe

it will display general protection fault. In previous version it will only gpf if run from another folder like this:

d:\>c:\myscript_secure.exe

If your script is in C:\ you have to grant the Exe Admin-Rights that should also be the reason why temp File could not been deleted.

[superman8855]

Originally Posted by Shadow992

If your script is in C:\ you have to grant the Exe Admin-Rights that should also be the reason why temp File could not been deleted.

Sorry, I dont really understand that. What is that mean?
I am running WinXP where no limitation for what I can do at c:\
Afterall, I'm login as an administrator (without password).

Temp file also in a folder that I can write. There is no such an issue on previous version

edit: just tried the newest version on a different folder (temp folder instead of c:\), it didn't work like reported. At the same time, I test the previous version, confirmed that previous version doesn't have the same issue

[Shadow992]

Originally Posted by superman8855

Sorry, I dont really understand that. What is that mean?
I am running WinXP where no limitation for what I can do at c:\
Afterall, I'm login as an administrator (without password).

Temp file also in a folder that I can write. There is no such an issue on previous version

edit: just tried the newest version on a different folder (temp folder instead of c:\), it didn't work like reported. At the same time, I test the previous version, confirmed that previous version doesn't have the same issue

#Updated
- Now it is possible to rename file (just as normal) even without my program
- Some changes to running program over cmd

Just try it again.

Edit:
Though you are running Vista/Win 7.

[link]

bin die letzten wochen bisschen busy :D
utf-8, neue autoit betas und dein tool sind drin, bin aber trotzdem noch nicht ganz fertig, dauert bisschen in asm (vllt. liegt's auch an mir :)

[superman8855]

Originally Posted by Shadow992

#Updated
- Now it is possible to rename file (just as normal) even without my program
- Some changes to running program over cmd

Just try it again.

Edit:
Though you are running Vista/Win 7.

Perfect. Running great on WinXP, hasn't test it on Win7 yet.
This is the best version ever until now.

The temp file still not deleted, but not a big deal, just a matter of one time press the del button

Thank you, thank you, thank you, Shadow

Originally Posted by link

bin die letzten wochen bisschen busy
utf-8, neue autoit betas und dein tool sind drin, bin aber trotzdem noch nicht ganz fertig, dauert bisschen in asm (vllt. liegt's auch an mir

Nice to have you here, Link

Why dont you stop release a new version of Exe2Aut?

[Shadow992]

Originally Posted by superman8855

Perfect. Running great on WinXP, hasn't test it on Win7 yet.
This is the best version ever until now.

The temp file still not deleted, but not a big deal, just a matter of one time press the del button

Thank you, thank you, thank you, Shadow



Nice to have you here, Link

Why dont you stop release a new version of Exe2Aut?

Dont worry next version is already under development and if everything is working like I want to then also next version will be a challenge for link I think. I really hope it. Buts lets see.

[superman8855]

Good day, Shadow.
I found another glitch on the protector. I have a compiled script that obfuscated using latest official AutoIT obfuscator version 1.0.30.4, when run the protected script it will shown AutoIT error window with this error message: "Error: Array variable has incorrect number of subsripts or subscript dimension range exceeded."

The original script is pretty simple, only consist of 88 lines, I just use it for testing.

No such error if not obfuscated.

Do I need to send the test script to you? How?

Edit: aha! I just realized something: is this error because obfuscated need FileInstall while our latest protector still has no support for FileInstall?

[Shadow992]

Originally Posted by superman8855

Good day, Shadow.
I found another glitch on the protector. I have a compiled script that obfuscated using latest official AutoIT obfuscator version 1.0.30.4, when run the protected script it will shown AutoIT error window with this error message: "Error: Array variable has incorrect number of subsripts or subscript dimension range exceeded."

The original script is pretty simple, only consist of 88 lines, I just use it for testing.

No such error if not obfuscated.

Do I need to send the test script to you? How?

Edit: aha! I just realized something: is this error because obfuscated need FileInstall while our latest protector still has no support for FileInstall?

Yes it is because of FileInstall.