Jump to content


ahk 2 exe


  • Please log in to reply
14 replies to this topic

#1 Guest

Guest
  • Guests

Posted 18 July 2012 - 08:12 PM

Hello,

I always thought the ahk2exe program would convert my .ahk script that no one could read it if he opens the exe to edit it.

But the script itself is in the .exe file with all the other stuffs:

.ahk:
MsgBox Hallo

.exe:

....
;
MsgBox Hallo
....
PAPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD


I am a little bit confused now.. I know that the converting to an exe is no protection at all but I dont want the people using my program to edit the scour code as soon as they download it.

Anything i can do?

#2 Guests

  • Guests

Posted 18 July 2012 - 09:10 PM

use mpress

#3 Guest

Guest
  • Guests

Posted 18 July 2012 - 09:21 PM

Yeah, that at least removed the msgbox, hello code.

What about the rest? I dont even know what that is and what is it good for?
"

By the way, something else i can do to protect it a little bit more?
I read about compiling your script by urself with an own algorithm.

How would i do that and would it be worth the work?

#4 Klark92

Klark92
  • Members
  • 854 posts

Posted 18 July 2012 - 10:44 PM

Lexikos's ahk2exe system is very simple ... source code can steal by anyone .. Use Basic version .. I hate it ...

#5 nimda

nimda
  • Members
  • 4301 posts

Posted 19 July 2012 - 12:17 AM

There is NO WAY to protect your source code. NONE. Not with AHK Basic, not with AHK_L. The reason for this is that "compiling" merely wraps the script and an interpreter together. The script must be read in plaintext by the interpreter at some time, at which point the script can be extracted. Furthermore, there are simple ways to extract the code from an exe compiled with mpress or /NoDecompile.

#6 MasterFocus

MasterFocus
  • Moderators
  • 4126 posts

Posted 19 July 2012 - 12:31 AM

On a related note, I Google'd for something like "interpreted code protection" and found this:
<!-- m -->http://www.google.co...tents/US7093119<!-- m -->
:shock:

#7 Klark92

Klark92
  • Members
  • 854 posts

Posted 19 July 2012 - 12:35 AM

@nimda : you say you can extract if it /Nodecompiled ?

@MasterFocus : so what can we do after read this :)

#8 girlgamer

girlgamer
  • Moderators
  • 2039 posts

Posted 19 July 2012 - 12:38 AM

There are entire industries built around this and this. Nothing is safe from a diligent, persistent thief.

#9 MasterFocus

MasterFocus
  • Moderators
  • 4126 posts

Posted 19 July 2012 - 12:41 AM

@MasterFocus : so what can we do after read this :)

Nothing really, I guess.
Just wanted to share a (perhaps) interesting related info, since there's been quite some search for code protection methods around here lately.

#10 Roninz

Roninz
  • Guests

Posted 19 July 2012 - 03:55 AM

Nothing is actually 100% safe. But you can still mpress it.. That will still save code from many people.. Other way can be to obfuscate it to make people bored like hell if they read it..

#11 Guest

Guest
  • Guests

Posted 19 July 2012 - 02:28 PM

As I said, I know it's not 100% protectable.

But come on, right clicking on it and then reading the source is no protection at all.

I appreciated the link to the MPRESS.

Any other ideas to make it more protected vs the 'public'?

#12 nimda

nimda
  • Members
  • 4301 posts

Posted 19 July 2012 - 02:41 PM

@nimda : you say you can extract if it /Nodecompiled ?

Yes, and it takes less than 60 seconds

#13 G. Sperotto

G. Sperotto
  • Members
  • 467 posts

Posted 19 July 2012 - 03:05 PM

Any other ideas to make it more protected vs the 'public'?


Yes.

And by the way, i don't think Mpress protection is even hard to Reverse Engineer (RE) because it's main focus is not Anti-RE protection, but rather size reduction. You should look for a packer that is more aimed towards protection instead. Study the candidates in this list and choose one that better focus on the protection side.

And some other things to keep in mind:

1 - Try and Obfuscate the code.
2 - Do a research on software RE. Knowing the main concepts involved in code stealing should greatly expand your ideas on how to protect your code.

#14 Klark92

Klark92
  • Members
  • 854 posts

Posted 19 July 2012 - 04:00 PM

@G. Sperotto:
it's an encrypted DllCall function .. so you can not script all project like this ..

#15 G. Sperotto

G. Sperotto
  • Members
  • 467 posts

Posted 19 July 2012 - 04:10 PM

@G. Sperotto:
it's an encrypted DllCall function .. so you can not script all project like this ..


I was referring the concepts of Obfuscation, not specifically on DllCall().