...

[stuka]

.

Edited August 23, 2009 by stuka

[qazwsx]

use a resource hacker maybe?. Its also good to remove all connections between your script and autoit. That way people won't even know they can decompile it.

[Toady]

I would recommend obfuscating your source code.

Here

[SmOke_N]

Why not just use the latest beta, and not concern yourself with it?

[GEOSoft]

Why not just use the latest beta, and not concern yourself with it?

I think the latest release is the same as far as decompile is concerned.

[GEOSoft]

But I can only use UPX to compress it after resource hacking it right? One the problems is that the icon somehow became ugly, probably to the compression. I've tried it though(your method) and it works.

Maybe that's the 2nd layer of security, but how do we prevent ppl ultimately from dicompiling it? Or how do they do it? I've of ppl using Au2Exe or Exe2Au to perform this even when a passphrase is no provided(by the cracker). Is it true?

As we've pointed out. The latest version does not readily decompile. If someone wants to use a hex editor against your code there is nothing that can be done.

[SmOke_N]

I think the latest release is the same as far as decompile is concerned.

24th August, 2007 - v3.2.6.0

* Changed: IconId in all GUI functions is now the same as GUICtrlSetImage().

WARNING: Previous scripts using GUICtrlSetImage(), GUISetIcon(), TraySetIcon() and TraySetPauseIcon()

may display a wrong Icon. To get the same icon "if nId > 0 Then newId = - nId - 1".

* Changed: AutoIt .a3x and compiled script format. Exe2Aut will only decompile 3.2.5.1

Are you saying that 3.2.7 put the option back in?

Edit:

I think I misunderstood you..., I think you were agreeing with me, just stating the newest release as well carries on with the above mentioned.

Edited August 27, 2007 by SmOke_N

[Toady]

But I can only use UPX to compress it after resource hacking it right? One the problems is that the icon somehow became ugly, probably due to the compression. I've tried it though(your method) and it works.

Maybe that's the 2nd layer of security, but how do we prevent ppl ultimately from dicompiling it? Or how do they do it? I've heard of ppl using Au2Exe or Exe2Au to perform this even when a passphrase is no provided(by the cracker). Is it true?

No matter the cause, there is always someone out there smart enough to reverse engineer your code. Your best bet is to confuse the hell outta them. I still recommend obfuscating it.

[big_daddy]

Is it possible to decompile a script using Exe2Au even though if I unticked the 'allow decompile' option?

For now only v3.2.5.1 and earlier can be decompiled even though "allow decompile" is unchecked.

Edit: earlier not later (Thanks Smoke!)

Edited August 27, 2007 by big_daddy

[SmOke_N]

For now only v3.2.5.1 and later can be decompiled even though "allow decompile" is unchecked.

Do you mean 3.2.5.1 and earlier?

[GEOSoft]

Are you saying that 3.2.7 put the option back in?

Edit:

I think I misunderstood you..., I think you were agreeing with me, just stating the newest release as well carries on with the above mentioned.

Yep!! You misunderstood but you got it the second time.

[big_daddy]

Do you mean 3.2.5.1 and earlier?

Yes that is what I meant.

[Jos]

do u mean the newer Exe2Au can actually decompile the older version .exes without a password?

no... that's not what is meant.

As of 3.2.5.2 the AUT2EXE is changed and there is no Passphrase and Allow Decompile option anymore because the stored format changed.

The supplied EXE2AUT will only decompile script made before 3.2.5.2 and still requires the Passphrase when that was used.

Jos

Edited August 27, 2007 by JdeB

[GEOSoft]

do u mean the newer Exe2Au can actually decompile the older version .exes without a password?

You're just not catching on. Right now only scripts compiled with versions up to and including 3.2.5.1 can be decompiled using Exe2Aut.

Also there is NO 100% sure way of preventing someone from reverse engineering code and it makes no difference if it's AutoIt or some other. It also makes no difference if you have a password set or not. With a password set on a compiled au3 script then Exe2Aut will not decompile it. A password will not prevent other methods from being employed. Just use the latest version of AutoIt (obfuscation helps) and quit worrying about it. Your code will be as safe as it gets.