clean text in the EXE file

[usera]

Greeting,

Did anybody know that once I compiled the au3 to exe file, will that exe file still hold the clean text or not? for example in the au3 file I have one line:

$file = FileOpen("C:\Program Files\Adobe\Reader 9.0\Reader\Javascripts\JSByteCodeWin.bin", 2)

once compiled to EXE file can I use like winhex to view that information. if yes, how to prevent that ?

Thanks

[usera]

Did anybody has ideas about this?

[Zedna]

Look at _StringEncrypt()

[Melba23]

usera,

Searching the forums will provide you with a lot more information in greater detail, but in brief:

- Your plain language script is within the compiled .exe, but in compressed form. It is not immediately viewable with a hex editor, but is by no means secure as it is expanded in memory when the .exe is run.

- Obfuscator (part of the full SciTE4AutoIt3 package) will obscure your script by changing variable and constant names (and a lot more!), which makes it harder to decompile but again does not render the .exe secure.

So, compiling an Autoit script will prevent quick snooping, but a determined, experienced hacker can relatively easily get your source - including passwords, specific filenames, etc.

M23

P.S. Please do not bump your own threads within 24 hrs. :-)

[Juvigy]

So? Any pointers how we can made a compiled .exe file difficult for a "a determined, experienced hacker " to see the code or mess with it?

[Valuater]

So? Any pointers how we can made a compiled .exe file difficult for a "a determined, experienced hacker " to see the code or mess with it?

The pointers are above as Melba stated, other than that...

compile with a different compiler, or make one

( don't ask, there are none to point you to, AFAIK )

8)

[Jos]

So? Any pointers how we can made a compiled .exe file difficult for a "a determined, experienced hacker " to see the code or mess with it?

You did read the post above yours?

Other than that: Enough is said on this subject so just search and read.

Edited April 20, 2009 by Jos