Is it a good Idea to use this tool anymore?
Unfortunately it got "cracked" too. So using this tool is not recommended anymore.
So it is not a good idea to only use this tool.
With newest AutoIt-Version this tool is working again like a charm, so just use it and cant be decompiled. :D (it may not work with newest autoit version because of autoit intern changes, there is at the moment no workaround known, i would have to update files but i do not know if ill update them...)
You should have instead a look at this thread to find some better solutions for protecting your files:
[Only registered and activated users can see links. Click Here To Register...]
Unfortunately it got "cracked" too. So using this tool is not recommended anymore.
So it is not a good idea to only use this tool.
With newest AutoIt-Version this tool is working again like a charm, so just use it and cant be decompiled. :D (it may not work with newest autoit version because of autoit intern changes, there is at the moment no workaround known, i would have to update files but i do not know if ill update them...)
You should have instead a look at this thread to find some better solutions for protecting your files:
[Only registered and activated users can see links. Click Here To Register...]
So guys, I finally managed to make another tool which now disables Links-Decompiler, too. So if you now use my old tool (Safe.exe) and my new Tool (SecureAu3.exe) no official decompiler will be able to decompile your scripts.
Even if you try to decompile by hand or just to decompile with olly or similiar tools, it will be hard. I just added also some Anti-Debugging-Features to the created Exe-File, which will run whenever a debugger is attached or even just if Links decompiler is attached.
This will also make the life much harder for reverse engineering.
That is why i hope and also i think that this tool will much longer make your autoit scripts secure than my old one (Safe.exe) did.
To give the best protection to your AutoIt-File and also the lowest Antivirus-Count, you have to do the following steps (please do not change the order otherwise your exe can get corrupted):
1. Use my old tool (Safe.exe)
2. Use my new tool (SecureAu3.exe)
There are some things you have to pay attention to:
- At first this will only work for x86 files and non UPX-packed AutoIt-Files.
- You may have to grant the created exe administration rights.
- Your AutoIt-File will get bigger.
- You must use Safe.exe before you can use this tool otherwise the created file will be corrupted.
- It works for XP, Vista, Win 7 and Win 8.
- There are False-Positive-Virus-Warnings:
[Only registered and activated users can see links. Click Here To Register...]
- You need "SecureAu3.exe" and "Executor.exe" in the same directory and you are not able to rename any of these tools. Later on after using my tool you can just release the created Exe-File you do not have to release Executor or SecureAu3, too. So if you want to release an AutoIt-File just release as always only the AutoIt-Exe itself.
- You should turn off your AntiVirus-System while using SecureAu3.exe otherwise it may block the script.
Things that have to be tested:
1. Win 2000 and lower.
All things that i mentioned are in the .zip-File in the attachments.
Edit:
If you use the tool called "Protecter.exe" you do not have to start my old tool "Safe.exe" first, because "Protecter.exe" will automatically run Safe.exe and will make your scripts ready to process further.
A video that explains how to use that program:
If you want more solutions to prevent stealing your AutoIt-Code:
[Only registered and activated users can see links. Click Here To Register...]
FAQ (German):
Credits:
Changelog:
Even if you try to decompile by hand or just to decompile with olly or similiar tools, it will be hard. I just added also some Anti-Debugging-Features to the created Exe-File, which will run whenever a debugger is attached or even just if Links decompiler is attached.
This will also make the life much harder for reverse engineering.
That is why i hope and also i think that this tool will much longer make your autoit scripts secure than my old one (Safe.exe) did.
To give the best protection to your AutoIt-File and also the lowest Antivirus-Count, you have to do the following steps (please do not change the order otherwise your exe can get corrupted):
1. Use my old tool (Safe.exe)
2. Use my new tool (SecureAu3.exe)
There are some things you have to pay attention to:
- At first this will only work for x86 files and non UPX-packed AutoIt-Files.
- You may have to grant the created exe administration rights.
- Your AutoIt-File will get bigger.
- You must use Safe.exe before you can use this tool otherwise the created file will be corrupted.
- It works for XP, Vista, Win 7 and Win 8.
- There are False-Positive-Virus-Warnings:
[Only registered and activated users can see links. Click Here To Register...]
- You need "SecureAu3.exe" and "Executor.exe" in the same directory and you are not able to rename any of these tools. Later on after using my tool you can just release the created Exe-File you do not have to release Executor or SecureAu3, too. So if you want to release an AutoIt-File just release as always only the AutoIt-Exe itself.
- You should turn off your AntiVirus-System while using SecureAu3.exe otherwise it may block the script.
Things that have to be tested:
1. Win 2000 and lower.
All things that i mentioned are in the .zip-File in the attachments.
Edit:
If you use the tool called "Protecter.exe" you do not have to start my old tool "Safe.exe" first, because "Protecter.exe" will automatically run Safe.exe and will make your scripts ready to process further.
A video that explains how to use that program:
|
|
If you want more solutions to prevent stealing your AutoIt-Code:
[Only registered and activated users can see links. Click Here To Register...]
FAQ (German):
1. Wie genau funktioniert das Programm und was muss ich bei den 3 AutoIt-Exe angeben?
Quote:
Ich steige nicht durch :-/
Ich habe mein AI3 Projekt kompiliert, ergo hab ich eine exe. Safe-Starter.exe fragt aber nach 4 Dateien.
Was will es von mir?
Ziehe ich meine exe einfach stumpf in die Safe.exe, wird mir eine neue erstellt. Diese wiederrum ist auf meinem Rechner (x64) nicht lauffähig.
Dann brauchst du aber noch 3 andere AutoIt-Skripts, die du auch kompilierst. Anschließend wählst du in der ersten Zeile deine Exe aus, die gesichert werden soll und in den anderen Zeilen wählst du die anderen Exen aus. Diese Exen werden dann wenn man versucht es zu decompilieren, decompiliert anstatt deinem original Skript.
Natürlich könnte ich auch feste Skripts in meine Safe.exe machen, aber das wäre so unsicher, dass es schon wieder nutzlos wäre.
Deshalb musst du selbst Skripts aussuchen/machen.
Credits:
Thanks to Jeoni for his help
Changelog:
v0.0.1
- Added some checks for errors in Protecter.exe
v0.0.2
- Added UPX-packing to the project
- Added AutoIt-Icon to the created file (Icon can be changed by Res-Hacker e.g.)
- Added some security things to Executor and SecureAu3
- Made Protecting faster
v0.1.0
- Added more Anti-Debugging-Routines
- Added major Source-Code-Protection-Improvements
- Removed popping up cmd
- Removed more false positive Virus warnings:
[Only registered and activated users can see links. Click Here To Register...]
v0.1.1
- Removed a bug where it was not possible to execute protected scripts in different directories
- Changed just some little security things
- Made Safe.exe crash less
v0.1.2
- Added more security things
- Added CUI support
- Added Win 7/Vista-Style-Support
v0.1.3
- Added even more security things
- Added full CUI support (Now Consoleread/Write and so on works too)
- Removed false positive Virus-Warnings which were in v0.1.3
- CopyRight and FileVersion is now copied from AutoIt-Script to protected Exe
- Changed Icon (just think this one looks better :D)
- Added possibility to use commandline in AutoIt-Scripts (just fixed problems with that I did not implement it ;))
v0.1.4
- Fixed some problems with cmd
- Added a little bit more text to Protecter.exe/.au3
v0.1.5
- Now it is possible to rename file (just as normal) even without my program
- Some changes to running program over cmd
v0.2.0
- Made Safe.exe better in protection and removed crashes
- Added FileInstall-Support
- CMD will now only appear if you select "CUI"
- Removed just some little Bugs
v0.2.1
- Made protection better (Thanks to Jeoni)
- Changed some things and made them more stable (Thanks to Jeoni)
- Removed some bugs (Thanks to Jeoni)
- Added some checks for errors in Protecter.exe
v0.0.2
- Added UPX-packing to the project
- Added AutoIt-Icon to the created file (Icon can be changed by Res-Hacker e.g.)
- Added some security things to Executor and SecureAu3
- Made Protecting faster
v0.1.0
- Added more Anti-Debugging-Routines
- Added major Source-Code-Protection-Improvements
- Removed popping up cmd
- Removed more false positive Virus warnings:
[Only registered and activated users can see links. Click Here To Register...]
v0.1.1
- Removed a bug where it was not possible to execute protected scripts in different directories
- Changed just some little security things
- Made Safe.exe crash less
v0.1.2
- Added more security things
- Added CUI support
- Added Win 7/Vista-Style-Support
v0.1.3
- Added even more security things
- Added full CUI support (Now Consoleread/Write and so on works too)
- Removed false positive Virus-Warnings which were in v0.1.3
- CopyRight and FileVersion is now copied from AutoIt-Script to protected Exe
- Changed Icon (just think this one looks better :D)
- Added possibility to use commandline in AutoIt-Scripts (just fixed problems with that I did not implement it ;))
v0.1.4
- Fixed some problems with cmd
- Added a little bit more text to Protecter.exe/.au3
v0.1.5
- Now it is possible to rename file (just as normal) even without my program
- Some changes to running program over cmd
v0.2.0
- Made Safe.exe better in protection and removed crashes
- Added FileInstall-Support
- CMD will now only appear if you select "CUI"
- Removed just some little Bugs
v0.2.1
- Made protection better (Thanks to Jeoni)
- Changed some things and made them more stable (Thanks to Jeoni)
- Removed some bugs (Thanks to Jeoni)