It's on, junge!
Dann geht auch unser bitch-fight weiter :)
Dann geht auch unser bitch-fight weiter :)
I got same error with this but your AutoIt Obfuscator work perfectly to meQuote:
Hi, I also have a problem with autoIt 3.3.10
running safe.exe returns this on the command prompt:
Thanks for the great work so far!PHP Code:Error: 1Press any key to continue . . .
edit: same error with or without antivirus.
Then use it. ;)Quote:
Thank you,
I really want to use your security solution.
You could have a look at all my other tools. I were Mod some time ago too.Quote:
But I can not afford to do that.
It's too dangerous ...
What really bothers me is that your software is identified as a virus in 60% of all anti-virus softwares.
It seems too fishy ...
It is because its similiar to a generic packer/crypter with Anti-Debugging functions.Quote:
You have to give me a convincing explanation why your software is identified as a virus in 60% of antivirus softwares.
Nice try mate xDQuote:
and i want to get a the piece of code(in your software) that causes exactly this problem.
This means that many of these functions(that viruses use too) are available to the public..Quote:
It is using many of the functions that viruses use too.
x86 works on 64 and 32 Bit so for me it does not make sense to use x64.Quote:
OK..
This means that many of these functions(that viruses use too) are available to the public..
so it should be no problem for you to give me a list of all these functions if they are puplic..
if so then please give this information because it will help me to trust you.
In addition,
I read it will not work with x64 exe.
this is still true? if so then i can't use it..
Because AutoIt file gets packed but does not matter this security solution got cracked by Aut2Exe so you should not use it anymore. Just use Obfuscators instead.Quote:
Why file install function isn't working when protected... Original file seems to work but when i protect it, the file install function don't work.
I am happy to tell you you're wrong.Quote:
Because AutoIt file gets packed but does not matter this security solution got cracked by Aut2Exe so you should not use it anymore. Just use Obfuscators instead.
I will post Source-Code but not now. Because there are many things that were done quick and dirty and I have to comment things otherwise no one will ever understand it. xDQuote:
I am happy to tell you you're wrong.
It is true that the solution will not defeat now Exe2Aut.
But your solution effectively hides the fact that the exe file is a AutoIt compiled exe.
so this is still good idea to use it just for hiding this fact.
but because my program must be compiled to 64bit (because in my case my the software use several functions that must work in 64 bit)
I can't use your solution.
In addition, your solution make the exe file to be identified as a virus by a lot ant-virus programs.
Because of these facts, it is good idea that you will develop a solution that is not designed to defeat Exe2Aut but still designed to hide the fact that the exe is AutoIt exe.
This way, you can delete several anti-debugging and decompiltion techniques(Because the goal is only to hide that the exe file is AutoIt)
and other functions that not required now.
and this can cause to less false positives by anti-virus.
I ask you to rebuild this security solution but without all the unnecessary stuff that cause to false positives and i want that the solution will be for 64bit also.
this may not defeat Exe2Aut. but it will enough to hide this fact and less false positives.
It should not be a big deal for you because you already know how to do it ..
You just have to do it again but without any anti-decompiltion techniques.
And I'd appreciate it if you post the source code (in this way I will start learn C++)