Someone decompiled my script...

[Thuiswerker]

I use AutoIt for many month now and i make realy nice programs.

But today i discovered that someone has decompiled my script, while i did not allowed decompiling when i compiled the script. Now my script has become public......

How can that be?

[BigDod]

There is a cracked de-compiler out on the web somewhere. If you search the forums for decompile you will find many topics on the issue.

[gamepin126]

I believe Smoke fixed that, so there's no way to tell it's an actual script.

[Thuiswerker]

I believe Smoke fixed that, so there's no way to tell it's an actual script.

In which version it is fixed ? i'm using 1.1.131 BETA

[gamepin126]

No, he made something that will patch your compiled exe so that it's not detected as an autoit script, I don't know where it is.

[Thuiswerker]

No, he made something that will patch your compiled exe so that it's not detected as an autoit script, I don't know where it is.

Okay, thanx.. i'm gonna try to find it!!

[Danny35d]

Jon already fix that problem, I can remember on what Beta version but, you can use now the new AutoIt realese 3.0.2.1

[Jon]

No, it's not fixed. I believe there is a hacked decompiler that works with the current version.

As part of the changes I'm working on at the moment is storing the script in a token form that the autoit engine can work with but that can't be easily converted back into text form. Exe2Aut won't be able to read it back so that means that someone would have to write a converter from scratch which is much harder.

[ShonGail]

Hello

if a script must contain sensitives informations as passwords, what is the best way to store them ?

Compiling a script (with passwords visible into the code) is it an acceptable way ?

Thanks

[SmOke_N]

Hello

if a script must contain sensitives informations as passwords, what is the best way to store them ?

Compiling a script (with passwords visible into the code) is it an acceptable way ?

Thanks

There is no "safe" way to store passwords currently, there are alternative measures, some use EnCodeIt... some use Files/Registry/Ini(s) to store their information... they encrypt it upon output, and decrypt from within the .exe upon input... unfortunately, your source is laid wide open, so the decryption functions are right there for anyone to play with... If/When Jon finishes what he's doing, this would be a great step having a more secure .exe.

[FeReNGi]

EnCodeIt works just fine for me, no need for extra security wich slow down compiling and executing.

[themax90]

EnCodeIt works just fine for me, no need for extra security wich slow down compiling and executing.

What about Assign, Execute, and Eval (and others) that won't work when you use it?

[ParoXsitiC]

I have decompiled a backup I had when I lost the original. I was able to find a hacked decompiler that worked with the lastest beta.

[ivan]

I was aware there was a solution a while back, but it seems the cat and mouse game never ends.

I think it must be hard for jon to weigh out what he can tell us without compromising his solution. In any case, I think if someone can, jon can.

ivan